182
submitted 11 months ago* (last edited 11 months ago) by along_the_road@beehaw.org to c/technology@beehaw.org
top 33 comments
sorted by: hot top new old
[-] Midnitte@beehaw.org 61 points 11 months ago

We just need IANA to add that new status code. /s

[-] lena@gregtech.eu 6 points 11 months ago
[-] Midnitte@beehaw.org 5 points 11 months ago
[-] lena@gregtech.eu 2 points 11 months ago* (last edited 11 months ago)

That's an HTTP status code, I know what those are :P

[-] Midnitte@beehaw.org 1 points 11 months ago

When laypeople see "404" I think they generally think of something other than "status" code, but I suppose you are correct.

[-] TehPers@beehaw.org 4 points 11 months ago

I think it also doesn't help that only 4XX (client error) and 5XX (server error) are defined as error status codes, and 4XX errors don't even necessarily indicate that anything happened that shouldn't happen (need to reauth, need to wait a bit, post no longer exists, etc).

Trying to think of what 6XX would stand for, and we already have "Service Unavailable" and "Bad Gateway"/"Gateway Timeout", so I guess 6XX would be "incompetence errors". 600 is "Bad Implementation", 601 is "Service Hosted On Azure", 602 is "Inference Failure" (for AI stuff), and I guess 666 is "Cloudflare Outage".

[-] prole@lemmy.blahaj.zone 46 points 11 months ago

I like that the headline needs to include the date so people know this is not an article from a few weeks ago.

[-] SweetCitrusBuzz@beehaw.org 24 points 11 months ago* (last edited 11 months ago)

Stop using it already. The internet was not meant to be centralised.

[-] boonhet@sopuli.xyz 15 points 11 months 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 11 points 11 months 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?

[-] along_the_road@beehaw.org 20 points 11 months ago
[-] Megaman_EXE@beehaw.org 20 points 11 months ago

Is there a reason these outages seem to have increased recently?

[-] pinball_wizard@lemmy.zip 15 points 11 months 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 13 points 11 months ago* (last edited 11 months ago)

From the blog post OP linked in a comment:

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 19 points 11 months 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 12 points 11 months ago* (last edited 11 months 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 own code/product and the developer of that thing isn't fixing the bug.

[-] kent_eh@lemmy.ca 7 points 11 months ago* (last edited 11 months ago)

Without looking into this specific outage, I'd suggest things like deferred maintenance and "cost optimizing" technical staffing are often contributing factors. (At least in my experience)

[-] Blackmist@feddit.uk 2 points 11 months ago

Lack of NSA funding to run their man in the middle platform that everyone likes.

[-] altphoto@lemmy.today 19 points 11 months ago

Interesting! That's why my ....penis! Exactly! Thanks Mr autocorrect!

That why the website I was trying to visit wasn't working!

[-] TehPers@beehaw.org 6 points 11 months ago

That's why your what wasn't working?

[-] thingsiplay@beehaw.org 13 points 11 months ago

Is this an off season April Fool's joke?

[-] along_the_road@beehaw.org 10 points 11 months ago
[-] TehPers@beehaw.org 16 points 11 months ago

TL;DR: React broke the internet.

Well, that, but also Cloudflare went down because they were trying to fix React's shit.

[-] mavu@discuss.tchncs.de 7 points 11 months 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 4 points 11 months ago

There is now a blog post from cloudflare on the outage: https://blog.cloudflare.com/5-december-2025-outage/

[-] Lojcs@piefed.social 3 points 11 months ago
[-] bufalo1973@piefed.social 2 points 11 months ago

Welcome to weekend Spain

this post was submitted on 05 Dec 2025
182 points (100.0% liked)

Technology

43908 readers
158 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 4 years ago
MODERATORS