[clairegraham]

We were down (downforeveryoneorjustme.com) completely, but back up now (as of a few minutes ago). Our domain wasn't even resolving; we use Cloudflare for frontend and DNS.

We had a surge of people checking if Discord was down on our site, then I noticed everything went down shortly after. Discord is still the top check right now.

I can't ever remember hitting these kind of traffic numbers before.

[ricardo81]

Interesting data you get in the face of adversity, providing your host resolves!

[Avalaxy]

Funny, I tried to use your site because the website I was trying to access stopped working. But your site was also down so I figured it was just my internet being cranky :/

[wcchandler]

I enjoy your service. Have you ever thought about expanding your offerings? I would love to see a recreation of "Internet Pulse"

[clairegraham]

Thanks! Yep, we have a lot of things on the todo. We want to add more user-focused / location-based outage information since our site is still too reliant on simple HTTP checks to report downtime. This is especially a problem with a Discord outage, for example, where the frontend website is not down, but there might be problems with the API, apps, or other components.

And I'd like to be able to have our site communicate outages like this Cloudflare one, where more than one site might be affected by a larger provider. Automating that is difficult.

This is still a side project, though, so I mostly work on it when I get the urge :)

[wcchandler]

That would be pretty interesting. Being able to drill down into individual pieces of a stack would be very informative, especially from a parent source. I bet a lot of services would even have that information readily available in their documentation for APIs.

How comfortable are you with open source? If you were willing to release your stack on Gitlab/Github, it might be worth your while.