We just need IANA to add that new status code. /s
Cloudflare is down [Dec 5]
Submitted 1 day ago by along_the_road@beehaw.org to technology@beehaw.org
https://www.cloudflarestatus.com/
Comments
Midnitte@beehaw.org 1 day ago
lena@gregtech.eu 19 hours ago
HTML error code?
Midnitte@beehaw.org 17 hours ago
djmikeale@feddit.dk 9 hours ago
Megaman_EXE@beehaw.org 20 hours ago
Is there a reason these outages seem to have increased recently?
pinball_wizard@lemmy.zip 10 hours ago
Is there a reason these outages seem to have increased recently?
We’ve had three years of unnecessary tech layoffs.
Nobody knows how the fuck anything in their technology stack works anymore.
Everyone is just spinning the giant wheel over and over and hoping it doesn’t land on bankrupt.
Sell your technology stocks, kids.
t3rmit3@beehaw.org 15 hours ago
From the blog post:
We made an unrelated change that caused a similar, longer availability incident two weeks ago on November 18, 2025. In both cases, a deployment to help mitigate a security issue for our customers propagated to our entire network and led to errors for nearly all of our customer base.
It seems that the method they have of specifically propagating new security configurations to their servers is not a gradual or group-based rollout, it pushes certain changes to all servers at once, so uncaught bugs end up hitting everything instead of just some initial test group.
In particular, the projects outlined below should help contain the impact of these kinds of changes:
Enhanced Rollouts & Versioning: Similar to how we slowly deploy software with strict health validation, data used for rapid threat response and general configuration needs to have the same safety and blast mitigation features. This includes health validation and quick rollback capabilities among other things.
“Fail-Open” Error Handling: As part of the resilience effort, we are replacing the incorrectly applied hard-fail logic across all critical Cloudflare data-plane components. If a configuration file is corrupt or out-of-range (e.g., exceeding feature caps), the system will log the error and default to a known-good state or pass traffic without scoring, rather than dropping requests. Some services will likely give the customer the option to fail open or closed in certain scenarios. This will include drift-prevention capabilities to ensure this is enforced continuously.
TehPers@beehaw.org 14 hours ago
This is the actual answer with respect to Cloudflare. Their config system was fucked in November. It’s still fucked in December. React’s massive CVE just forced them to use it again.
More generally, the issue is a matter of companies forcefully accelerating feature development at the cost of stability, likely due to AI. This is how the company I’m at is like anyway.
Kolanaki@pawb.social 20 hours ago
Something they (Cloudflare) said recently about the last big outage is that there is some bug in some part of their system that isn’t their code/product and the developer of that thing isn’t fixing the bug.
Megaman_EXE@beehaw.org 19 hours ago
Interesting! Thanks for the information.
kent_eh@lemmy.ca 20 hours ago
Without looking into this specific outage, I’d suggest things like deferred maintenance and “cost optimizing” technocal staffing are often contributing factors. (At least in my experience)
Blackmist@feddit.uk 17 hours ago
Lack of NSA funding to run their man in the middle platform that everyone likes.
altphoto@lemmy.today 19 hours ago
Interesting! That’s why my …penis! Exactly! Thanks Mr autocorrect!
That why the website I was trying to visit wasn’t working!
SweetCitrusBuzz@beehaw.org 23 hours ago
Stop using it.
boonhet@sopuli.xyz 23 hours ago
On the one hand, I 110% agree with you
On the other hand, it’s so damn convenient. They cache your shit and they protect you from DDoS attacks, and they do it for free*
*Until you’re big enough to warrant extortion from them.
pheggs@feddit.org 20 hours ago
I am pretty sure that 99% of sites would have less downtime due to DDoS attacks than from such outages. I have so many issues with Cloudflare that I don’t even know where to begin with, from over-caching causing issues up to decrypting all traffic, who the hell thinks this is really a good idea?
mavu@discuss.tchncs.de 5 hours ago
It seems my moving away from major tech companies is working well, I didn’t even notice there was an outage (again).
along_the_road@beehaw.org 1 day ago
downdetector.com also down
thingsiplay@beehaw.org 1 day ago
Is this an off season April Fool’s joke?
along_the_road@beehaw.org 17 hours ago
There is now a blog post from cloudflare on the outage: blog.cloudflare.com/5-december-2025-outage/
along_the_road@beehaw.org 1 day ago
TehPers@beehaw.org 1 day ago
TL;DR: React broke the internet.
Well, that, but also Cloudflare went down because they were trying to fix React’s shit.
Lojcs@piefed.social 1 day ago
it’s back
bufalo1973@piefed.social 1 day ago
Welcome to weekend Spain
prole@lemmy.blahaj.zone 23 hours ago
I like that the headline needs to include the date so people know this is not an article from a few weeks ago.