Live data from Hacker News

Show HN: I made a down detector for down detector

downdetectorsdowndetector.com

81–90 of 184 posts

Re: Show HN: I made a down detector for down detector

#81
post #75
post #47

Earlier quoted context omitted.

I think cloudflare has billions worth of incentives to be reliable however they can slip up, it happens and that's why centralization is bad.

That is true. However, I would say that the effect of this outage on customer retention will be (relatively) smaller than it would be for a smaller CDN.

Maybe? Maybe not? It depends on the nature of the outage and how motivated their customers are to switch over to a new service.

Re: Show HN: I made a down detector for down detector

#82
post #80

As a European solo developer, I’ve switched entirely to European alternatives for all my infrastructure since the beginning of the year. Cloudflare > Bunny.net AWS > Hetzner Business email > Infomaniak Not a single client site has experienced downtime, and it feels great to finally decouple from U.S. services.

Are you using a US-based transactional email service like Twilio? Curious about EU-based alternatives.

There are self hostable alts to twillio

Re: Show HN: I made a down detector for down detector

#83
post #71
post #65

Earlier quoted context omitted.

> I don't quite think companies realize how bad it would be if EG AWS was hacked. I don't think they'd care. Companies only care about one thing: stock price. Everything rolls up into that. If AWS got hacked and said company was affected by it, it wouldn't be a big deal because they'd be one of many and they'd be lost in the crowd. Any hit to their stock/profits would be minimal and easily forgotten about. Now, if th…

> Companies only care about one thing: stock price. Its rarely affected in any case. Take a look at the Crowdstrike price chart (or revenue or profits). I think most people (including investors) just take it for granted that systems are unreliable and regard it as something you live with.

I think that's more of a indicator that it hasn't effected their business. They lost nearly 1/5 of their stock price after that incident (obviously not accounting for other factors; I'm not a stock analyst). Investors thought they'd lose customers and reacted in obvious fashion.

But it's since been restored. According to the news, they lost very little customers over the incident. That is why their stock came back. If they continued having problems, I doubt it would have been so rosy. So yes, to your point, a blip here or there happens.

Re: Show HN: I made a down detector for down detector

#84
post #55

This is GOLD Jerry, Gold. but who detects the down detector detecting the down detector detecting the down detector

I know you were joking, but responding in seriousness - while in general it's worthwhile asking "Quis custodiet ipsos custodes?", in this particular case, I don't see any issue with Down Detector detecting the Down Detector Down Detector. Assuming they are in different availability zones, using different code, with a different deployment cadence, this approach works quite well in practice.

Re: Show HN: I made a down detector for down detector

#85
post #75

Earlier quoted context omitted.

That is true. However, I would say that the effect of this outage on customer retention will be (relatively) smaller than it would be for a smaller CDN.

Maybe? Maybe not? It depends on the nature of the outage and how motivated their customers are to switch over to a new service.

The good news is that we're just living in a perfect natural experiment:

Cloudflare just caused a massive internet outage costing millions of dollars worldwide, in part due to a very sloppy mistake that definitely ought to have been prevented (using Rust's “unwrap” in production ). Let's see how many customers they lose because of that and we'll see how big are their incentives. (If you look at the evolution of their share value, it doesn't look like the incident terrified their shareholders at least…)

Re: Show HN: I made a down detector for down detector

#87
post #34

Earlier quoted context omitted.

I would guess yes, unless you have a server with unlimited file descriptors and flawless connectivity to every other AS...

But CDNs are made for static content so your comment means I can't run a dynamic website unless I have unlimited file descriptors and flawless connectivity.

"Need" is a strong word. But I think the point is that if you expect wildly spikey traffic/don't want the site to go down if it receives a very sudden influx of requests, going static is a very good answer, much cheaper than "serverless" or over-provisioning.

Re: Show HN: I made a down detector for down detector

#89
post #55

This is GOLD Jerry, Gold. but who detects the down detector detecting the down detector detecting the down detector

I know you were joking, but responding in seriousness - while in general it's worthwhile asking "Quis custodiet ipsos custodes?", in this particular case, I don't see any issue with Down Detector detecting the Down Detector Down Detector. Assuming they are in different availability zones, using different code, with a different deployment cadence, this approach works quite well in practice.

> Quis custodiet ipsos Custodes?

Arbites.

Re: Show HN: I made a down detector for down detector

#90
post #80

As a European solo developer, I’ve switched entirely to European alternatives for all my infrastructure since the beginning of the year. Cloudflare > Bunny.net AWS > Hetzner Business email > Infomaniak Not a single client site has experienced downtime, and it feels great to finally decouple from U.S. services.

Are you using a US-based transactional email service like Twilio? Curious about EU-based alternatives.

Hello, You can test Sweego - https://www.sweego.io/ We (I'm the CTO) are fully European Bye Pierre-Yves
Post reply on HN