163 points
59 minutes ago
| 25 comments
| HN
reconnecting
37 minutes 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!

reply
emsixteen
12 minutes ago
[-]
I have it pointed at my domains just for basic stuff and luckily that seems to be working at least.
reply
aurareturn
19 minutes ago
[-]
We use Render which apparently uses Cloudflare. It went down.

Hard to know what 3rd party services you depend on uses Cloudflare.

reply
torginus
17 minutes ago
[-]
Raise your hands if you found out you use cloudflare three weeks ago.
reply
reconnecting
18 minutes ago
[-]
Luckily there is Privacy terms that usually disclose this.
reply
llama052
31 minutes ago
[-]
I’d argue that the big 3 cloud providers have more outages than this, only cloudflare actually lets you know.
reply
reconnecting
26 minutes ago
[-]
I've been operating a relatively small digital platform for 15 years. We don't use Cloudflare, for bots, we use tirreno (1), which we specifically created to filter malicious traffic.

For hosting, we use a local and sovereign EU provider.

If tomorrow Cloudflare, Amazon, and Microsoft were to somehow disappear or go permanently down, I wouldn't even notice.

1. https://github.com/tirrenotechnologies/tirreno

reply
balupton
14 minutes 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.

reply
Eldodi
17 minutes ago
[-]
How crazy is it that Lime bikes become unusable if Cloudflare goes down? I hope Waymos are not on cloudflare
reply
saretup
15 minutes ago
[-]
If Waymos do not use local models it would be a horrible decision.
reply
hyperbolablabla
16 minutes ago
[-]
Seems incredibly irresponsible if you ask me...
reply
jakewins
56 minutes ago
[-]
reply
ponys
28 minutes ago
[-]
This happening exactly when the ticket sale for Evanescence was happening, in which the payment method was hosted on Cloudflare was really funny,
reply
TACIXAT
34 minutes ago
[-]
Chess dot com was affected, I got a Cloudflare internal server error at the end of one of my matches.
reply
stacktrace
29 minutes ago
[-]
Will you consider it a stalemate if no party is able to make any further moves?
reply
manojlds
17 minutes ago
[-]
Btw a Chess Olympiad was declared drawn and shared winners after internet issues.
reply
TACIXAT
21 minutes ago
[-]
I would have probably considered whoever was up material as the winner, as long at there was sufficient time left.

I guess it had an active connection through the game end though, maybe web sockets. I was afraid it wasn't recorded because I played quite well!

reply
nurettin
25 minutes ago
[-]
There are actual rules for stalemate, so it would probably just be a draw.
reply
reassess_blind
23 minutes ago
[-]
Probably an abort. Draw awards Elo.
reply
dwayne_dibley
17 minutes ago
[-]
hahaha, this is how I found out too!
reply
Akronymus
53 minutes ago
[-]
reply
nsiradze
22 minutes ago
[-]
This needs to be changed, whole web was stopped working - it's a big responsibility and Cloudflare should acknowledge it.
reply
willsmith72
55 minutes ago
[-]
including downdetector... that's annoying https://downdetector.com/status/npm/
reply
philipp-gayret
51 minutes ago
[-]
And https://downdetectorsdowndetector.com says that https://downdetector.com/ is up! >:( What a world we live in
reply
phito
43 minutes ago
[-]
reply
tomudding
40 minutes ago
[-]
reply
frizlab
31 minutes ago
[-]
I really expected that one to be a joke
reply
nolok
32 minutes ago
[-]
Good god, what have we done ...
reply
nurettin
28 minutes ago
[-]
This is now my favorite post on HN
reply
cyanydeez
33 minutes ago
[-]
Turtles!(Expletive!)
reply
KptMarchewa
33 minutes ago
[-]
reply
nickdothutton
19 minutes ago
[-]
Complexity is the enemy of availability (and security, and a few more things besides).
reply
gblargg
18 minutes ago
[-]
Maybe some company could start up that had decentralized backups/mirrors/caches of websites in case cloudflare goes down...
reply
rohannn
36 minutes ago
[-]
Is perplexity down too as a result of this? Seeing mixed reports
reply
pietz
35 minutes ago
[-]
It means half of the internet isn't (wasn't) working.
reply
rodwyersoftware
17 minutes ago
[-]
HB1 in action
reply
jansan
17 minutes 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.
reply
rifycombine1
32 minutes ago
[-]
Gitlab is affected as well :(
reply
Morizero
29 minutes ago
[-]
Yeah affected me too. I have code to push dang it!!!
reply
programmexxx
19 minutes ago
[-]
why tinyurl.com was down...
reply
santiagobasulto
39 minutes ago
[-]
Docker Hub is affected as well
reply
gem4508
37 minutes ago
[-]
LinkedIn was also affected.
reply
andrewl-hn
13 minutes ago
[-]
You would think they would use Azure for CDN, but apparently not.
reply
georgestrakhov
40 minutes ago
[-]
we are back up I think
reply
alexander2002
35 minutes ago
[-]
Am I tripping cuz I saw this a while ago
reply
Buttons840
28 minutes ago
[-]
reply
sammy2255
34 minutes ago
[-]
Im thinking the same thing..
reply
yapyap
41 minutes ago
[-]
Hm, it’s over.
reply
swagmoose
20 minutes ago
[-]
who else was woken up in the middle of the night for on-call pages because of cloudflare?
reply
rzmmm
21 minutes ago
[-]
Another Option::unwrap incident perchance?
reply
mhovd
40 minutes ago
[-]
And now it is back up
reply
darkamaul
29 minutes 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

reply
rvba
16 minutes ago
[-]
They probably jusr reverted last change?
reply
antonvs
22 minutes ago
[-]
> “only” lasted 35 minutes

That single incident drops their uptime to four nines. Combine it with other recent incidents and they’re probably at three nines. That’s amateur level.

> that's quite an impressive achievement

No it isn’t. Good grief.

reply
gowthamgts12
27 minutes ago
[-]
it affected CDN services as well, i don't know or understand why that's not mentioned in the status page.
reply
powerpixel
26 minutes ago
[-]
Having this kind of outage on a friday after what happened last month though is not a good thing... Props to them for getting back up so quickly but come on, these kinds of outages were not a thing a while back.
reply