Live data from Hacker News

Cloudflare was down

cloudflare.com

321–330 of 560 posts

Re: Cloudflare was down

#321
post #210
post #9

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

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

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

Re: Cloudflare was down

#323

So, 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…

Nobody is being forced to use Cloudflare

Re: Cloudflare was down

#325
post #76

That's the 30% vibe code they promised us. Cynicism aside, something seems to be going wrong in our industry.

Also “Rewrite it in Rust”. P.S. it’s a joke, guys, but you have to admit it’s at least partially what’s happening

Did you consider to rewrite your joke in rust?

Re: Cloudflare was down

#326
post #214

Earlier quoted context omitted.

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

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

I work for a small company. We have no written SLA agreements.

Re: Cloudflare was down

#328
post #25

This is not good. One major outage? Something exceptional. Several outages in a short time? As someone thats worked in operations, I have empathy; there are so many “temp havks” that are put in place for incidents. but the rest of the world won’t… they’re gonna suffer a massive reputation loss if this goes on as long as the last one.

Probably fired a lot of their best people in the past few years and replaced it with AI. They have a de-facto monopoly, so we'll just accept it and wait patiently until they fix the problem. You know, business as usual in the grift economy.

The "AI agents" are on holiday when an outage like this happens.

Re: Cloudflare was down

#329
post #192

Earlier quoted context omitted.

Yeah that's a hard 500 right? Not even Cloudflare's 500 branded page like last time. What could have caused this, I wonder.

I hope it’s not another Result.unwrap().

maybe this would cause rust to adopt exception handling, and by exception I mean panic

Re: Cloudflare was down

#330

So, 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…

Let your hoster take care of the DDoS and stop using the flaky behemoth.

You haven't actually watched Mad Max, have you? I do recommend it.

Post reply on HN