Cloudflare had a partial outage
111–120 of 448 posts
Re: Cloudflare had a partial outage
#112Yes, not worldwide but a lot of places. Problem with our backbone. We know what. Rollbacks etc. happening. Bring it back up in chunks. Should be back up everywhere.
Re: Cloudflare had a partial outage
#113Re: Cloudflare had a partial outage
#114CF's website is down as well. The CF Status page [0] says everything is working, though. [0] https://www.cloudflarestatus.com/
I don't think I've ever seen a status page report an issue at the time the issue was occurring. Seems a bit pointless.
(Also it doesn't help that uptime monitoring systems are usually stupid and love triggering on false positives)
Re: Cloudflare had a partial outage
#115Re: Cloudflare had a partial outage
#116Re: Cloudflare had a partial outage
#117Yes, not worldwide but a lot of places. Problem with our backbone. We know what. Rollbacks etc. happening. Bring it back up in chunks. Should be back up everywhere.
Re: Cloudflare had a partial outage
#118Re: Cloudflare had a partial outage
#119At times like this and the big Fastly outage roughly a year ago, choosing to host on a simple, independent bare-metal box doesn't seem like such a bad strategy (as long as one has backups for disaster recovery, of course). Sure, other things can cause downtime in that kind of infrastructure, but at least my service isn't likely to be taken offline by someone else's configuration error or deployment gone wrong.
I do think there is some holistic overview of hosting stuff on the internet, where you could label each extra actor that can break things, mitigation strategies, and costs of such. Someone better than me would be able to place relative risk (and I think in that model laying out various provider uptimes/issues would be great!) and offer a smart way of dealing with the buy vs. build question on this.
Re: Cloudflare had a partial outage
#120Yes, not worldwide but a lot of places. Problem with our backbone. We know what. Rollbacks etc. happening. Bring it back up in chunks. Should be back up everywhere.