Live data from Hacker News

Cloudflare had a partial outage

cloudflare.com

111–120 of 448 posts

Re: Cloudflare had a partial outage

#112

Yes, 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.

We are not using cloud flare. But our domain is also not accessible. We are using digital ocean's DNS service for propagating our IP. Does the DigitalOcean's DNS service depend on Cloudflare service?

Re: Cloudflare had a partial outage

#114
post #17
post #9

CF'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.

Because most of them are manually updated, and not pulling directly from an uptime system (at least for incidents, etc)

(Also it doesn't help that uptime monitoring systems are usually stupid and love triggering on false positives)

Re: Cloudflare had a partial outage

#117

Yes, 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.

Just wanted to also reiterate how thankful I am that you took your time to let us know. It speaks volumes.

Re: Cloudflare had a partial outage

#119

At 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.

What is your setup to where you are isolated from "other person making a mistake"? Even if you're a box in a colocated datacenter you're still able to get knocked off the net from some maintenance on the surrounding pipes. Hell, hosting your own box doesn't cause Comcast DNS issues to not knock off a bunch of people either.

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.

Post reply on HN