zlacker

>>AlphaW+(OP)
Putting your status page on a separate domain for availability reasons: good

Not updating that status page when the core domain goes down: less good

>>dmatti+L3
You'd be surprised how often those pages are updated manually. By the person on call who has other things to take care of first.

>>troupo+Pu
Because a healthcheck ping every X seconds is too difficult to implement for a GitHub sized company? There they have it now. Useless status page...

>>Myster+NH
You quickly start to get into "what does down mean?" conversations. When you have a bunch of geographical locations and thousands of different systems/functionalities, it's not always clear if something is down.

Take a service responding 1% of the time with errors. Probably not "down". What about 10%? Probably not. What about 50%? Maybe, hard to say.

Maybe there's a fiber cut in rural village effecting 100% of your customers there but only 0.0001% of total customers?

Sure there's cases like this where everything is hosed but it sort of begs the question "is building a complex monitoring system for <some small number of downtimes a year>" actually worth it?