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

391–400 of 560 posts

Re: Cloudflare was down

#391

Post by ozim »

netdevphoenix wrote: post #333
lucianbr wrote: post #288

Earlier quoted context omitted.

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?

Anyone who doesn't have any choice financially or gnostically. Same reason why people pay Netflix despite the low quality of most of their shows and the constant termination of tv series after 1 season. Same reason why people put up with Meta not caring about moderating or harmful content. The power dynamics resemble a monopoly

Most of services are not really critical but customers want to have 99.999% on the paper.

Most of the time people will just get by and ignore even full day of downtime as minor inconvenience. Loss of revenue for the day - well you most likely will have to eat that, because going to court and having lawyers fighting over it most likely will cost you as much as just forgetting about it.

If your company goes bankrupt because AWS/Cloudflare/GCP/Azure is down for a day or two - guess what - you won't have money to sue them ¯\_(ツ)_/¯ and most likely will have bunch of more pressing problems on your hand.

Re: Cloudflare was down

#392

Post by JeremyJaydan »

I moved away from Cloudflare over a month ago because I didn't understand how they don't have pricing caps for their upgraded plans, they genuinely seem like the mob but I haven't looked any further into it..

Either way it's been interesting to see the bullets I've been dodging.

Re: Cloudflare was down

#394

Post by mike_hearn »

kortilla wrote: post #377
zwnow wrote: post #351

Earlier quoted context omitted.

The first one had something to do with Rust :-)

Not really. In C or C++ that could have just been a segfault. .unwrap() literally means “I’m not going to handle the error branch of this result, please crash”.

Indeed, but fortunately there are more languages in the world than Rust and C++. A language that performed decently well and used exceptions systematically (Java, Kotlin, C#) would probably have recovered from a bad data file load.

Re: Cloudflare was down

#395

Post by cryptonym »

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…

> Looking forward to the post mortem

This is becoming a meme.

Re: Cloudflare was down

#396

Post by windward »

gwd wrote: post #381
koakuma-chan wrote: post #197

Earlier quoted context omitted.

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

A lot of words for a 'might'. We don't know what caused the downtime.

Re: Cloudflare was down

#398

Post by jjude »

JeremyJaydan wrote: post #392

I moved away from Cloudflare over a month ago because I didn't understand how they don't have pricing caps for their upgraded plans, they genuinely seem like the mob but I haven't looked any further into it.. Either way it's been interesting to see the bullets I've been dodging.

What service(s) are you using now? What did you move to?

Re: Cloudflare was down

#399

Post by perching_aix »

gwd wrote: post #381
koakuma-chan wrote: post #197

Earlier quoted context omitted.

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

[dead]

Re: Cloudflare was down

#400

Post by meandmycode »

cryptonym wrote: post #395
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…

> Looking forward to the post mortem This is becoming a meme.

This has to be setting off some alarm bells internally, a well written postmortem on an occasional issue, great, but when your postmortem talks about learnings and improvements yet major outages keep happening, it becomes meaningless..
Post reply on HN