zlacker

[return to "Github.com is down"]
1. dmatti+L3[view] [source] 2023-06-29 17:52:35
>>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

◧◩
2. troupo+Pu[view] [source] 2023-06-29 19:47:06
>>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.
◧◩◪
3. Myster+NH[view] [source] 2023-06-29 20:53:20
>>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...
◧◩◪◨
4. virapt+aL[view] [source] 2023-06-29 21:11:45
>>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.

[go to top]