> Monitoring - A fix has been implemented and we are monitoring the results. > Dec 05, 2025 - 09:12 UTC
Yeah, cloudflare.com is working and the website that first clued me in to the outage (chess.com) is also working.
Cloudflare was down
361–370 of 560 posts
Re: Cloudflare was down
#362Yes. Weird that https://www.cloudflarestatus.com/ isn't reporting this properly. It should be full of red blinking lights.
Yeah. I only work for a small company, but you can be certain we will not update the status page if only a small portion of customers are affected, and if we are fully down, rest assured there will be no available hands to keep the status page updated
if we are fully down, rest assured there will be no available hands to keep the status page updated
There is no quicker way for customers to lose trust in your service than it to be down and for them to not know that you're aware and trying to fix it as quickly as possible. One of the things Cloudflare gets right is the frequent public updates when there's a problem.
You should give someone the responsibility for keeping everyone up to date during an incident. It's a good idea to give that task to someone quite junior - they're not much help during the crisis, and they learn a lot about both the tech and communication by managing it.
Re: Cloudflare was down
#363what's the estimated loss? any guesses or estimations?
Re: Cloudflare was down
#364Looking forward to the post mortem on this one. We weren't affected (just using the CDN), and people are saying they weren't affected who are using Cloudflare Workers (a previous culprit which we've since moved off), so I wonder what service / API was actually affected that brought down multiple websites with a 500 but not all of them. Wise was just down which is a pretty big one. Also odd how some websites were down…
we were not affected too and we realised it was Cloudflare because Linear was down and they were mentioning an upstream service. Also Ecosia was affected, and I then realised they might be relying on Cloudflare too.
Re: Cloudflare was down
#365Re: Cloudflare was down
#366That's the 30% vibe code they promised us. Cynicism aside, something seems to be going wrong in our industry.
Salaries are flat relative to inflation and profits. I've long felt that some of the hype around "AI" is part of a wage suppression tactic.
Re: Cloudflare was down
#367Earlier 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....
downdetectorsdowndetectors didn't detect breakdown of downdetectors with 500 Error
Re: Cloudflare was down
#368Earlier quoted context omitted.
>rest assured there will be no available hands to keep the status page updated That's not how status pages if implemented correctly work. The real reason status pages aren't updated is SLAs. If you agree on a contract to have 99.99% uptime your status page better reflect that or it invalidates many contracts. This is why AWS also lies about it's uptime and status page. These services rarely experience outages accordi…
This is weird - at this level contracts are supposed to be rock solid so why wouldn't they require accurate status reporting? That's trivial to implement, and you can even require to have it on a neutral third-party like UptimeRobot and be done with it. I'm sure there are gray areas in such contracts but something being down or not is pretty black and white.
> I'm sure there are gray areas in such contracts but something being down or not is pretty black and white.
Is it? Say you've got some big geographically distributed service doing some billions of requests per day with a background error rate of 0.0001%, what's your threshold for saying whether the service is up or down? Your error rate might go to 0.0002% because a particular customer has an issue so that customer would say it's down for them, but for all your other customers it would be working as normal.
Re: Cloudflare was down
#369Looking forward to the post mortem on this one. We weren't affected (just using the CDN), and people are saying they weren't affected who are using Cloudflare Workers (a previous culprit which we've since moved off), so I wonder what service / API was actually affected that brought down multiple websites with a 500 but not all of them. Wise was just down which is a pretty big one. Also odd how some websites were down…
CDN was also affected for some customers. we were down with 500.
Re: Cloudflare was down
#370So, I understand correctly that all websites and services want protection from DDoS attacks, and that's basically their number one concern. The second is caching in different parts of the world. So, it's caching and DDoS. But at the same time, nobody wants to use CloudFront from AWS because it’s not that simple yet. And it’s more expensive, while Cloudflare is free. So, what should we do about all this? This won’t do…
Someone should make an open source system that lets you easily host containers so that if one fails, we can easily switchover across providers. Like Vercel AI SDK but for containers. That is, if docker isnt failing (it is right now cause it depends on Cloudflare)