Anyone shorting the damn stock?
Cloudflare was down
161–170 of 560 posts
Re: Cloudflare was down
#162Just in time for the London work day :)
Re: Cloudflare was down
#163Every time Cloudflare is down I'm not sure if it's really down or not because most down detector websites use Cloudflare. Lmao
Re: Cloudflare was down
#164This is not a good look, at all
Re: Cloudflare was down
#165Yes. Weird that https://www.cloudflarestatus.com/ isn't reporting this properly. It should be full of red blinking lights.
There is an update:
"Cloudflare Dashboard and Cloudflare API service issues"
Investigating - Cloudflare is investigating issues with Cloudflare Dashboard and related APIs.
Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed. Dec 05, 2025 - 08:56 UTC
Re: Cloudflare was down
#166Earlier quoted context omitted.
hmm... https://downdetectorsdowndetector.com/ (edit: it's working now (detecting downdetector's down))
So, This one is green: https://downdetectorsdowndetector.com This one is not openning: https://downdetectorsdowndetectorsdowndetector.com This one is red: https://downdetectorsdowndetectorsdowndetectorsdowndetector....
Re: Cloudflare was down
#167looks like a big one. interestingly, our site, which uses a TON of Cloudflare services[0] — yet not their front-line proxy — is doing fine: https://magicgarden.gg . So it seems like it's just the big ol' "throw this big orange reverse proxy in front of your site for better uptime!" is what's broken... [0] Workers, Durable Objects, KV, R2, etc
Moving off of Cloudflare for my personal domain is on my todo list for the holidays...
Re: Cloudflare was down
#168Odd
Re: Cloudflare was down
#169[deleted]
Re: Cloudflare was down
#170Earlier quoted context omitted.
> In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec 05, 2025 - 07:00 UTC Something must have gone really wrong.
It's 1AM in San Francisco right now. I don't envy the person having to call Matthew Prince and wake him up for this one. And I feel really bad for the person that forgot a closing brace in whatever config file did this.
Agreed, I feel bad for them. But mostly because cloudflare's workflows are so bad that you're seemingly repeatedly set up for really public failures. Like how does this keep happening without leadership's heads rolling. The culture clearly is not fit for their level of criticality