Live data from Hacker News

Cloudflare Down Again – and DownDetector Is Also Down

news.ycombinator.com

171–177 of 177 posts

Re: Cloudflare Down Again – and DownDetector Is Also Down

#171

Earlier quoted context omitted.

Not sure if this is related, but has anyone seen their allowance used up unexpectedly fast? Had Claude Code Web showing service disruption warnings, and all of a sudden I'm at 92% usage. I'm on the pro plan, only using Sonnet and Haiku. I almost never hit the 5-hour limit, let alone in less than 2 hours.

Did you accidentally hit tab to turn on “always thinking”? It burns tokens much faster.

No, I found the issue. It went all in on unit tests and wrote way too many.

Re: Cloudflare Down Again – and DownDetector Is Also Down

#172

I host my companys website on Cloudflare pages using Cloudflare's DNS. I don't want to move to 100% self hosting but I would like to have self hosted backup. Has anyone solved this?

Having a self-hosted “backup” that is ready to go at any time means having a self-hosted server that’s always on, basically. There are lots of cheap colo or VM options out there. But the problem is going to be dealing with an outage… how do you switch DNS over when your DNS provider is down? Well, one way is to use a different DNS provider than either of your hosting options. You can see this is getting complicated.…

> how do you switch DNS over when your DNS provider is down?

You list multiple nameservers.

    yoursite.com. 86400 IN NS ns1.yourprovider.com.
    yoursite.com. 86400 IN NS ns2.yourprovider.com.
    yoursite.com. 86400 IN NS ns1.yourotherprovider.com.
    yoursite.com. 86400 IN NS ns2.yourotherprovider.com.

Re: Cloudflare Down Again – and DownDetector Is Also Down

#173
post #73

Earlier quoted context omitted.

They’re a global company that offshores with location based pay and utilizes H1Bs. I think that’s the first thing to look at. You get what you pay for. Stop trying to devalue labor. Not much sympathy when you’re obviously cutting corners.

Just because someone is on an H1B visa doesn't mean they know less. It's a bit rich to blame this on foreign workers even though nothing is known about who or what caused this outage.

I think the implication is that people with connections who have no business touching production code are getting those jobs through fraud.

Re: Cloudflare Down Again – and DownDetector Is Also Down

#174

https://downdetectorsdowndetectorsdowndetectorsdowndetector.... reports that https://downdetectorsdowndetectorsdowndetector.com/ is down, guessing downdetectorsdowndetectorsdowndetector runs via cloudflare!

It's downdetectors all the way down

correction, it is downdetectors all the way downdetectors

Re: Cloudflare Down Again – and DownDetector Is Also Down

#175

Earlier quoted context omitted.

In my experience, the communication problems stem from the Americans who expect perfect English from all others. English is spoken across the entire business world between people for whom it is not their first language. The accents and broken English is epic in many organizations. Yet they work through it and get things done together. If you work harder at taking the burden upon yourself to understand others, you mig…

I have the same experience as you. I have been working with many non-native English speakers from different countries, and Americans (and to some degree Brits) are usually the ones who can't follow what is said. This improves over time as they get used to different accents, but it seems it is easier for non-native speakers to understand foreign accents than native speakers in general. I'm not saying I always understa…

Normally I have had very good experiences as well. My colleagues almost always speak very good English and even those who don't are understandable. Everyone is happy to conduct meetings (with many nationalities, as I work in a scientific field) in English.

Only once have I encountered a problem. A colleague berated me in front of others for speaking "difficult English" and accused me of doing this on purpose to cause trouble for them, instead of speaking proper international English like everyone else did. But, I am a native English speaker with an RP accent and we were all in England at the time, working for a British organisation. I was simply speaking normally and otherwise had no issue with this colleague, whose English was very good. I don't recall their having been any misunderstandings between us before.

Re: Cloudflare Down Again – and DownDetector Is Also Down

#176

Earlier quoted context omitted.

What are you implying by linking to that article?

Cloudflare was crowing that their services were better because “We write a lot of Rust, and we’ve gotten pretty good at it.” The last outage was in fact partially due to a Rust panic because of some sloppy code. Yes, these complex systems are way more complex than just which language they use. But Cloudflare is the one who made the oversimplified claim that using Rust would necessarily make their systems better. It’s…

You can write sloppy code using any language.

Re: Cloudflare Down Again – and DownDetector Is Also Down

#177

Earlier quoted context omitted.

This is generally BS apologetics for C. If that was in C this would have just been overrunning the statically allocated memory amount and would have resulted in a segfault. Rust did its job and forced them to return an error from the lower function. They explicitly called a function to crash if that returned an error. That’s not a rust problem.

We don't know how the C program would have coped. It could equally have ignored the extra config once it reached its maximum, which would cause new problems but not necessarily cause an outage. It could've returned an error and safely shut down the whole program (which would result in the same problem as Rust panicking). What we do know is Cloudflare wrote a new program in Rust, and never tested their Rust program wi…

> You can't say "Rust did its job" and blame the programmer,

You absolutely can. This is someone just calling panic in an error branch. Rust didn’t overrun the memory which would have been a real possibility here in C.

The whole point is that C could have failed in the exact same way but it would have taken extra effort to even get it to detect the issue an exit. For an error the programmer didn’t intend to handle like in this case, it likely would have just segfaulted because they wouldn’t bother to bounds check.

> TANSTAAFL

The way C could have failed here is a superset of how Rust would. Rust absolutely gives you free lunch, you just have to eat it.

Post reply on HN