Live data from Hacker News

Show HN: I made a down detector for down detector

downdetectorsdowndetector.com

91–100 of 184 posts

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

#92
post #30

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.

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…

> A lot of people want the brand recognition too.

Not to mention the familiarity of the company, its services and expectations. You can hire people with experience with AWS, Azure or GCP, but the more niche you go, the higher the possibility that some people you hire might not know how to work with those systems and their nuances, which is fine they can learn as they work, but that adds to ramp up time and could lead to inadvertent mistakes happening.

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

#93
post #50
post #40

Earlier quoted context omitted.

https://downdetectorsdowndetectorsdowndetectorsdowndetector....

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

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

#94
post #37
post #36

Earlier quoted context omitted.

I bet most people don't even need the extra features.

When forced to use AWS I only use the extra features I am specifically told to or that are already in use in order to make the system less tied to AWS and easier for me to manage (I am not an AWS specialist so its easier for me to just run stuff like I would on any server or VPS). I particularly dislike RDS (of things I have used). I like Lightsail because its reasonably priced and very like just getting a VPS. S3 is…

Looking forward to the Show HN: I built a web site that uses all of AWS services.

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

#97
post #26

Earlier quoted context omitted.

+1 for Scaleway. I also use Hetzner for most of my compute. But some stuff just really profits from using managed services. I‘ve used Scaleway‘s Serverless compute offers and managed DBs an been quite happy with them.

-1 for Scaleway, they were a really good deal years ago but have become expensive af

well they're not comparable to hetzner anymore, both in terms of features and price. only their dedibox brand could compare, as it's the classic hosting approach vs cloud.

for the hobby crowd it's a shame, for a corporation it's still cheaper than aws with the extra bonus of not having any tie to the us.

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

#98
post #49
post #42

Earlier quoted context omitted.

Big fan of bunny.net as CDN, however Cloudflare is my "smart" filter for all kind of attacks, AI scrapers, malicious traffic, etc. Am I missing something or is bunny.net not actually a replacement for that?

They've recently introduced bunny.net Shield to add a security layer. I've not made use of it yet so I don't know what the coverage is like or how effective it is: https://bunny.net/shield/

This is very interesting. Thank you for making me aware!

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

#99

Earlier quoted context omitted.

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.

"To serve the Emperor. To protect His domains. To judge and stand guard over His subjects. To carry the Emperor's law to all worlds under His blessed protection. To pursue and punish those who trespassed against His word."
Post reply on HN