Show HN: I made a down detector for down detector (downdetectorsdowndetector.com)

Article summary

A developer created a down detector for DownDetector, a website that checks the status of other websites. The new website is a tiny, independent status checker that monitors DownDetector's availability from multiple locations. It is not affiliated with DownDetector and is intended for entertainment purposes. The website has sparked a discussion about recursion and the potential for an infinite loop of down detectors.

Main themes

• DownDetector
• Recursion
• Website monitoring
• Cloudflare
• CDN
• Decentralization

What commenters say

• The creation of a down detector for DownDetector is a humorous example of recursion, highlighting the potential for an infinite loop of monitoring websites.
• Some commenters suggest that a distributed system of down detectors could provide a more robust solution for monitoring website availability.
• Others argue that a single, centralized down detector is sufficient and that the use of a CDN is not necessary for a simple, static website.
• There is a debate about the importance of decentralization and the potential risks of relying on centralized services like Cloudflare.
• Some commenters propose using alternative infrastructure services, such as European-based providers, to reduce dependence on US-based companies.
• The discussion also touches on the limitations of DNS and the potential for errors in domain name registration.