Live data from Hacker News

Show HN: I made a down detector for down detector

downdetectorsdowndetector.com

141–150 of 184 posts

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

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

Hyvor Relay (https://github.com/hyvor/relay) can be self-hosted. We are planning a cloud version for 2026. (I am a co-founder)

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

#142
post #30

Earlier quoted context omitted.

Those are all much smaller. Smaller providers have a much stronger incentive to be reliable, as they will lose customers if they are not. In a corporate settings management will say "this would not have happened if you had gone with AWS". its the current version of "no one ever got fired for buying IBM" (we had MS and others in between). Hetzner provides a much simpler set of services than AWS. Less complexity to go…

There is this weird thing that happens with hyperscale - the combination of highly central decision-making, extreme interconnection / interdependence of parts, and the attractiveness of lots of money all conspire to create a system pulled by unstable attractors to a fracturing point (slowed / mitigated at least a little by the inertia of such a large ship). Are smaller scale services more reliable? I think that's too…

Have you considered that a widespread outage is a feature, not a bug?

If AWS goes down, no one will blame you for your web store being down as pretty much every other online service will be seeing major disruptions.

But when your super small provider goes down, it's now your problem and you better have some answers ready for your manager. And you'll still be affected by the AWS outage anyways as you probably rely on an API that runs on their cloud!

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

#144
post #123

Earlier quoted context omitted.

> AWS and Cloudflare don't actually experience more downtime, it's just a bigger story when they are down because so many people use them. This may be true over a long enough timeframe, but GP stated that their clients had experienced no downtime since switching at the start of the year. That is clearly better than both AWS and Cloudflare during that time.

My clients (extremely large) AWS based infrastructure experienced no downtime this year. So, if it's based on some random person's clients, it's not clearly better at all. I don't use cloud flare for anything, so no comment there.

> So, if it's based on some random person's clients, it's not clearly better at all.

Valid. I should have made it clear that I meant "clearly better from GP's perspective."

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

#145
post #77

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.

As an American solo developer, I am close to doing the same. These mega-corps are out of control.

Out of control in what way?

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

#146

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.

I feel like a year is too short a time frame to measure reliability.

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

#147
post #93
post #50

Earlier quoted context omitted.

who is going to throw $10 at https://downdetectorsdowndetectorsdowndetectorsdowndetectors...

Had to check, but that is actually beyond what DNS allows. Labels (the part between dots) are limited to 63 characters. We could sneakily drop an s somewhere in there and then it would fit. https://datatracker.ietf.org/doc/html/rfc1035 Also I think I triggered a nice error log in domaintools just now. https://whois.domaintools.com/downdetectorsdowndetectorsdown...

Have to use more efficient notation - downdetectorsx5.com

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

#148
post #4

Yeah we had a good laugh when Downdetector was down during the Cloudflare outage yesterday. So this is appropriate. +1

I remember when the CDN I was working for had to change our status page provider when our first one became our client.

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

#149
post #111
post #30

Earlier quoted context omitted.

Those are all much smaller. Smaller providers have a much stronger incentive to be reliable, as they will lose customers if they are not. In a corporate settings management will say "this would not have happened if you had gone with AWS". its the current version of "no one ever got fired for buying IBM" (we had MS and others in between). Hetzner provides a much simpler set of services than AWS. Less complexity to go…

> Smaller providers have a much stronger incentive to be reliable, as they will lose customers if they are not. Hard disagree. A smaller provider will think twice about whether they use a Tier 1 data center versus a Tier IV data center because the cost difference is substantial and in many cases prohibitively expensive.

This. There's a fundamental logic error here. You simply don't hear about downtimes at smaller providers that often because it doesn't affect a significant portion of the internet like it does e.g. for AWS. But that doesn't mean they are more stable in general.

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

#150
post #93

Earlier quoted context omitted.

Had to check, but that is actually beyond what DNS allows. Labels (the part between dots) are limited to 63 characters. We could sneakily drop an s somewhere in there and then it would fit. https://datatracker.ietf.org/doc/html/rfc1035 Also I think I triggered a nice error log in domaintools just now. https://whois.domaintools.com/downdetectorsdowndetectorsdown...

Have to use more efficient notation - downdetectorsx5.com

fix.downdetectors.com
Post reply on HN