top | item 46158338

(no title)

163 points| wonderfuly | 2 months ago

discuss

order

reconnecting|2 months 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!

aurareturn|2 months ago

We use Render which apparently uses Cloudflare. It went down.

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

emsixteen|2 months ago

I have it pointed at my domains just for basic stuff and luckily that seems to be working at least.

llama052|2 months ago

I’d argue that the big 3 cloud providers have more outages than this, only cloudflare actually lets you know.

szundi|2 months ago

If that would be so simple

ponys|2 months ago

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

Eldodi|2 months ago

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

saretup|2 months ago

If Waymos do not use local models it would be a horrible decision.

hyperbolablabla|2 months ago

Seems incredibly irresponsible if you ask me...

TACIXAT|2 months ago

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

stacktrace|2 months ago

Will you consider it a stalemate if no party is able to make any further moves?

dwayne_dibley|2 months ago

hahaha, this is how I found out too!

balupton|2 months 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.

nsiradze|2 months ago

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

nickdothutton|2 months ago

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

rohannn|2 months ago

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

pietz|2 months ago

It means half of the internet isn't (wasn't) working.

gblargg|2 months ago

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

rifycombine1|2 months ago

Gitlab is affected as well :(

Morizero|2 months ago

Yeah affected me too. I have code to push dang it!!!

gem4508|2 months ago

LinkedIn was also affected.

andrewl-hn|2 months ago

You would think they would use Azure for CDN, but apparently not.

jansan|2 months 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.

yapyap|2 months ago

Hm, it’s over.

swagmoose|2 months ago

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

mhovd|2 months ago

And now it is back up

rzmmm|2 months ago

Another Option::unwrap incident perchance?

darkamaul|2 months 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

gowthamgts12|2 months ago

it affected CDN services as well, i don't know or understand why that's not mentioned in the status page.

powerpixel|2 months 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.

rvba|2 months ago

They probably jusr reverted last change?

antonvs|2 months 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.