163 points by wonderfuly 2 hours ago


reconnecting - an hour ago

Raise your hands if you don't use Cloudflare in your stack and are proud of your decision.

You are the future of the operational internet!

jakewins - 2 hours ago

Better link: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

Eldodi - an hour ago

How crazy is it that Lime bikes become unusable if Cloudflare goes down? I hope Waymos are not on cloudflare

balupton - an hour ago

If all you use them for is caching, then they could provide webhooks for their scheduled maintenance so customers can disable cloudflare during the maintenance and reenable it once it's all good.

However, for customers using other things, perhaps we need an independent cloudflare for cloudflare service that serves its own cache of your site when cloudflare is inaccessible.

Could combine the two ideas so when there is scheduled cloudflare maintenance, it switches dns to the cloudflare for cloudflare service that uses cloudflare if online but if cloudflare is offline then serves cache, and once cloudflare maintenance is finished then restore cloudflare dns.

Plex, Plexamp, and accounts in Sonos went down.

ponys - an hour ago

This happening exactly when the ticket sale for Evanescence was happening, in which the payment method was hosted on Cloudflare was really funny,

Akronymus - an hour ago

dupe https://news.ycombinator.com/item?id=46158191

willsmith72 - 2 hours ago

including downdetector... that's annoying https://downdetector.com/status/npm/

TACIXAT - an hour ago

Chess dot com was affected, I got a Cloudflare internal server error at the end of one of my matches.

nsiradze - an hour ago

This needs to be changed, whole web was stopped working - it's a big responsibility and Cloudflare should acknowledge it.

nickdothutton - an hour ago

Complexity is the enemy of availability (and security, and a few more things besides).

gblargg - an hour ago

Maybe some company could start up that had decentralized backups/mirrors/caches of websites in case cloudflare goes down...

rohannn - an hour ago

Is perplexity down too as a result of this? Seeing mixed reports

rodwyersoftware - an hour ago

HB1 in action

rifycombine1 - an hour ago

Gitlab is affected as well :(

santiagobasulto - an hour ago

Docker Hub is affected as well

gem4508 - an hour ago

LinkedIn was also affected.

georgestrakhov - an hour ago

we are back up I think

jansan - an hour ago

Looks like this time they first considered that they screwed up themselves, unlike the last time when they were fighting a phantom attack for a while until they realized that it was their own fault.

programmexxx - an hour ago

why tinyurl.com was down...

alexander2002 - an hour ago

Am I tripping cuz I saw this a while ago

yapyap - an hour ago

Hm, it’s over.

swagmoose - an hour ago

who else was woken up in the middle of the night for on-call pages because of cloudflare?

mhovd - an hour ago

And now it is back up

rzmmm - an hour ago

Another Option::unwrap incident perchance?

darkamaul - an hour ago

According to UpDog [0], the incident only lasted 35 minutes (8:40 - 9:15). And the Cloudflare status page seems to validate this timeline.

While down times are not ideal, that's quite an impressive achievement to be able to resolve an incident of this scale in minutes - not hours.

[0]: https://updog.ai/status/cloudflare