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
Making an official status change in a large organization can be kind of a big deal. Sometimes phrasing needs to be run by legal or customer-facing people. There can be contract implications.

Of course they should try to update their status page in a timely manner, but it is frequently manual from what I’ve seen.