top | item 46158206

(no title)

xyproto | 2 months ago

Yes.

Weird that https://www.cloudflarestatus.com/ isn't reporting this properly. It should be full of red blinking lights.

discuss

order

javier2|2 months ago

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

s_dev|2 months ago

>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 according their own figures but rather 'degraded performance' or some other language that talks around the issue rather than acknowledging it.

It's like when buying a house you need an independent surveyor not the one offered by the developer/seller to check for problems with foundations or rotting timber.

lawnchair|2 months ago

I have to say that if an incident becomes so overwhelming that nobody can spare even a moment to communicate with customers, that points to a deeper operational problem. A status page is not something you update only when things are calm. It is part of the response itself. It is how you keep users informed and maintain trust when everything else is going wrong.

If communication disappears entirely during an outage, the whole operation suffers. And if that is truly how a company handles incidents, then it is not a practice I would want to rely on. Good operations teams build processes that protect both the system and the people using it. Communication is one of those processes.

onion2k|2 months ago

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.

GoblinSlayer|2 months ago

You won't be able to update the status page due to failures anyway.

63stack|2 months ago

This is just business as usual, status pages are 95% for show now. The data center would have to be under water for the status page to say "some users might be experiencing disruptions".

csomar|2 months ago

They just did an update, and it is bad (in the sense that they are not realizing their clients are down?)

> Investigating - Cloudflare is investigating issues with Cloudflare Dashboard and related APIs.

> These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge.

> Customers using the Dashboard / Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.

yapyap|2 months ago

well it does say that now, so…

which datacenter got flooded?

chironjit|2 months ago

Yeah, their status site reports nothing but then clicking on some of the links on that site bring you the 500 error

mikkom|2 months ago

Company internal status pages are always like this. When you don't report problems they don't exist!

Havoc|2 months ago

It’s wild how non of the big corporations can make a functional status page

javier2|2 months ago

They could, but accurate reporting is not good for their SLAs

dncornholio|2 months ago

They can. They don't want to though.

jachee|2 months ago

Management is always going to take too long (in an engineer’s opinion) to manually throw the alerts on. They’re pressing people for quick fixes so they can claim their SLAs are intact.

hinkley|2 months ago

They were intending to start a maintenance window starting 6 minutes ago, but they were already down by then.

dinoqqq|2 months ago

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

rollulus|2 months ago

Not weird, that’s tradition by now.

jbuild|2 months ago

Interesting, I get a 500 if I try to visit coinbase.com, but my WebSocket connections to advanced-trade-ws.coinbase.com are still live with no issues.

emakarov|2 months ago

probably these websockets are not going through cloudflare

csomar|2 months ago

> 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.

headmelted|2 months ago

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.

shafyy|2 months ago

Life hack: Announce bug that brings your entire network down as scheduled maintenance.

devmor|2 months ago

Yes, the incident report claims this was limited to their client dashboard. It most certainly was not. I have the PagerDuty alerts to prove it...

fxd123|2 months ago

> Investigating - Cloudflare is investigating issues with Cloudflare Dashboard and related APIs.

They seem to now, a few min after your comment

redm|2 months ago

Im much more concerned with customer sites being down which indicates are not impacted. They are.. :/

tjpnz|2 months ago

They have enough data to at least automate yellow.

rvz|2 months ago

The AI agents can't help out on this time.

rifycombine1|2 months ago

maybe we can back to stackoverflow :)

jonathanlydall|2 months ago

Now showing a message, posted at 08:56 UTC.

tommek4077|2 months ago

Yes, it’s really ‘weird’ that they refuse to share any details. Completely unlike AWS, for example. As if being open about issues with their own product wouldn’t be in their best interest. /s