Today’s Cloudflare Outage, Vibe Coding, and a Year of Multi Billion-Dollar Incidents. In 1 year we had major issues from Crowdstrike, AWS, Azure, Google Cloud and now Cloudflare. Coincidence? I don't think so
Posted by Frequent-Football984@reddit | programming | View on Reddit | 15 comments
99ducks@reddit
Frequent-Football984@reddit (OP)
Not yet
99ducks@reddit
The public evidence points to it being triggered by a DDoS attack.
Frequent-Football984@reddit (OP)
Aren't they used especially for anti-DoS attacks? Isn't that ironic?
Expensive_Goat2201@reddit
No, it means they get DDOS'd constantly so your service doesn't. They have way more resources to withstand a ddos but a big enough one would eventually overwhelm them.
Frequent-Football984@reddit (OP)
The CTO responded
> "In short, a latent bug in a service underpinning our bot mitigation capability started to crash after a routine configuration change we made. That cascaded into a broad degradation to our network and other services. This was not an attack."
So no attack
Frequent-Football984@reddit (OP)
https://www.reddit.com/r/programare/comments/1p09qou/comment/nphavci/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Frequent-Football984@reddit (OP)
Here is the official response https://blog.cloudflare.com/18-november-2025-outage
Frequent-Football984@reddit (OP)
The CTO of Cloudflare responded:
"I won’t mince words: earlier today we failed our customers and the broader Internet when a problem in
u/Cloudflare
network impacted large amounts of traffic that rely on us. The sites, businesses, and organizations that rely on Cloudflare depend on us being available and I apologize for the impact that we caused.
Transparency about what happened matters, and we plan to share a breakdown with more details in a few hours. In short, a latent bug in a service underpinning our bot mitigation capability started to crash after a routine configuration change we made. That cascaded into a broad degradation to our network and other services. This was not an attack.
That issue, impact it caused, and time to resolution is unacceptable. Work is already underway to make sure it does not happen again, but I know it caused real pain today. The trust our customers place in us is what we value the most and we are going to do what it takes to earn that back.
"
https://x.com/dok2001/status/1990791419653484646
sweetnsourgrapes@reddit
When will Reddit provide a "flag as AI" button to help mods wade through this trash?
EC36339@reddit
Copilot, make me a study with some statistics on the correlation between major cloud outages in 2025 and the growing prevalence of vibe statistics, then generate a discussion of this study in the form of a typical thread on r/programming.
sweetnsourgrapes@reddit
Yup. "Important nuance:" is one thing that makes it pretty obvious. It's usually the lack of.. well, nuance, in the writing, and absence of the usual storytelling feel to a narrative that a human period produces.
Frequent-Football984@reddit (OP)
What if in a few days we see that it was an issue from vibe coding?
__Blackrobe__@reddit
If we ignore "correlation-causation" saying... guess what project managers will learn about their vibe coding obsession: nothing.
Frequent-Football984@reddit (OP)
I personally think it has to do with vibe coding on critical software parts. https://www.youtube.com/watch?v=4yDm6xNeYas