Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare was down

cloudflare.com

Post reply on HN
Print view View original

381–390 of 560 posts

Re: Cloudflare was down

#381

Post by gwd »

koakuma-chan wrote: post #197
nlitened wrote: post #130

Earlier quoted context omitted.

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

No, it has nothing to do with Rust.

But it might have something to do with the "rewrite" part:

> The idea that new code is better than old is patently absurd. Old code has been used. It has been tested. Lots of bugs have been found, and they’ve been fixed. There’s nothing wrong with it. It doesn’t acquire bugs just by sitting around on your hard drive.

> Back to that two page function. Yes, I know, it’s just a simple function to display a window, but it has grown little hairs and stuff on it and nobody knows why. Well, I’ll tell you why: those are bug fixes. One of them fixes that bug that Nancy had when she tried to install the thing on a computer that didn’t have Internet Explorer. Another one fixes that bug that occurs in low memory conditions. Another one fixes that bug that occurred when the file is on a floppy disk and the user yanks out the disk in the middle. That LoadLibrary call is ugly but it makes the code work on old versions of Windows 95.

> Each of these bugs took weeks of real-world usage before they were found. The programmer might have spent a couple of days reproducing the bug in the lab and fixing it. If it’s like a lot of bugs, the fix might be one line of code, or it might even be a couple of characters, but a lot of work and time went into those two characters.

> When you throw away code and start from scratch, you are throwing away all that knowledge. All those collected bug fixes. Years of programming work.

From https://www.joelonsoftware.com/2000/04/06/things-you-should-...

Re: Cloudflare was down

#382

Post by yoctosec »

runeb wrote: post #202
yoctosec wrote: post #115

I use Cloudflare because of their Tunnel to protect my Raspberry Pi, but I think I will just use it without the Tunnel now. My main concern is privacy, but I'm not ready to accept so frequent downtime and dependence on them. The whole reason to host self-host was to be independent anyway. Does anyone have a recommendation for that (that is free)? Should I worry about privacy? My name and my city are on the website an…

Checkout tailscale

And what about a website I want to make public? I'm just concerned about my IP being visible, like for my personal website or my searxng instance

Re: Cloudflare was down

#383

Post by reassess_blind »

madjam002 wrote: post #340

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

Yeah it's strange. My sites that are are proxied through Cloudflare remained up, but Supabase was taken offline so some backends were down. Either a regional PoP style issue, or a specific API or service had to be used to be affected.

Re: Cloudflare was down

#384

Post by archon810 »

madjam002 wrote: post #340

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

Our locations excluded from Cloudflare WAF were up, but the rest was down. I think WAF took a dump.

Re: Cloudflare was down

#385

Post by arjie »

How interesting. As of 00:30 or so I could still access Claude but then it went down with a 500 from Cloudflare and I thought I'd nab a quick something off Slickdeals but that's down too. My own blog is on Cloudflare's `cloudflared` tunnel and it's working just fine, even the cache, so it must be something hitting some specific type of configuration or some shard hitting some region.

And they're back before I finished the comment. Such a pity, I was hoping to hog some more Claude for myself through Claude Code.

Re: Cloudflare was down

#386

Post by esseph »

5d41402abc4b wrote: post #312
karmakurtisaani wrote: post #85

Earlier quoted context omitted.

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.

>They have a de-facto monopoly On what? There are lots of CDN providers out there.

They do fare more than just CDN. It's the combination of service, features, reach, price, and the integration of it all.

Re: Cloudflare was down

#387

Post by kryptn »

madjam002 wrote: post #340

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

was interesting, some of our stuff failed, but some other stuff that used cloudflare indirectly didn't.

Re: Cloudflare was down

#388

Post by devmor »

xyproto wrote: post #9

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

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

Re: Cloudflare was down

#389

Post by heipei »

lucianbr wrote: post #288
s_dev wrote: post #214

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

Are the contracts so easy to bypass? Who signs a contract with an SLA knowing the service provider will just lie about the availability? Is the client supposed to sue the provider any time there is an SLA breach?

The client is supposed to monitor availability themselves, that is how these contracts work.

Re: Cloudflare was down

#390

Post by themly »

madjam002 wrote: post #340

Looking 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 definitely down also. We were widely impacted by it with 500's.
Post reply on HN