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
Because a ping does not have a consistent behaviour and sometimes will fail because of networking issues at the source. If you enable pingdom checks for many endpoints and all available regions, prepare for a some false positives every week for example.

At that point it's worse than what you already know from your browser - it may show the service is having issues when you can access it, or that the service is ok when you can't.

>>virapt+aL
> At that point it's worse than what you already know from your browser - it may show the service is having issues when you can access it, or that the service is ok when you can't.

Worst case you have more data points to draw conclusions from. Status page red, works for me? Hmm, maybe that's why the engineers in the other office are goofing off on Slack. Status page green, I get HTTP 500s? Guess I can't do this thing but maybe other parts of the app still work?

>>ben0x5+gb1
So essentially in neither situation did you get any information that changes what you'd do next. If something fails, you'll probably try working on another part and see if that works anyway. The automated status provided you with no extra actionable info.