5 ms·

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

cruano 3y ago
Maybe the plumbing for updating the status page went down too
- dietr1ch 3y ago
  Right, but lack of good signals should be regarded as a bad signal too The status page backend should actively probe the site, not just being told what to say and keeping stale info around.
  - mysterydip 3y ago
    It probably did originally, until one time it showed down by mistake. Some manager somewhere said that's unacceptable, so it was changed to not happen.
traviscj 3y ago
maybe they used gitops
jiayo 3y ago
https://www.githubstatus.com/ https://www.githubstatus.com/
- slyall 3y ago
  https://www.githubstatus.com/incidents/gqx5l06jjxhp https://www.githubstatus.com/incidents/gqx5l06jjxhp
eYrKEC2 3y ago
I prefer https://downdetector.com https://downdetector.com . The users get to vote there. No corporate filtering ( ostensibly ) https://downdetector.com/status/github/ https://downdetector.com/status/github/
- darkerside 3y ago
  That's a really cool overview. Some charts have a very high variance, and others very low. I wonder whether that volatility is a function of volume of users/reports or of user technical savvy. Pretty interesting either way.
  - Ukv 3y ago
    Charts appear scaled by max value - high variance will probably be from background noise of random reports being scaled up without any actual outage causing a spike.
- Zamicol 3y ago
  Quis custodiet ipsos custodes?
  - metalliqaz 3y ago
    The users, apparently.
  - a1369209993 3y ago
    If you mean them going the Glassdoor/Yelp route and letting github et al buy the aforementioned corporate filtering, the assumption is that you'd eventually hear about it and stop trusting them, just like you should with Glassdoor and Yelp. If you just mean checking whether downdetector.com is down, obviously you have to use a different service for that. In either case, you should of course always have at least two custodes for cross-checking and backup purposes. (Which is the problem re Glassdoor and Yelp.)
  - RcouF1uZ4gsC 3y ago
    Hacker News and Twitter
troupo 3y ago
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.
- Mystery-Machine 3y ago
  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...
  - viraptor 3y ago
    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.
    - ben0x539 3y ago
      > 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?
      - viraptor 3y ago
        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.
  - naikrovek 3y ago
brasic 3y ago
I miss the old status page: https://web.archive.org/web/20170110044141/https://status.github.com/ https://web.archive.org/web/20170110044141/https://status.gi...
sotrue922 3y ago
[dead]

cruano 3y ago

Maybe the plumbing for updating the status page went down too

dietr1ch 3y ago
Right, but lack of good signals should be regarded as a bad signal too The status page backend should actively probe the site, not just being told what to say and keeping stale info around.
- mysterydip 3y ago
  It probably did originally, until one time it showed down by mistake. Some manager somewhere said that's unacceptable, so it was changed to not happen.

traviscj 3y ago

maybe they used gitops

jiayo 3y ago

https://www.githubstatus.com/ https://www.githubstatus.com/

slyall 3y ago
https://www.githubstatus.com/incidents/gqx5l06jjxhp https://www.githubstatus.com/incidents/gqx5l06jjxhp

eYrKEC2 3y ago

I prefer https://downdetector.com https://downdetector.com . The users get to vote there. No corporate filtering ( ostensibly ) https://downdetector.com/status/github/ https://downdetector.com/status/github/

darkerside 3y ago
That's a really cool overview. Some charts have a very high variance, and others very low. I wonder whether that volatility is a function of volume of users/reports or of user technical savvy. Pretty interesting either way.
- Ukv 3y ago
  Charts appear scaled by max value - high variance will probably be from background noise of random reports being scaled up without any actual outage causing a spike.
Zamicol 3y ago
Quis custodiet ipsos custodes?
- metalliqaz 3y ago
  The users, apparently.
- a1369209993 3y ago
  If you mean them going the Glassdoor/Yelp route and letting github et al buy the aforementioned corporate filtering, the assumption is that you'd eventually hear about it and stop trusting them, just like you should with Glassdoor and Yelp. If you just mean checking whether downdetector.com is down, obviously you have to use a different service for that. In either case, you should of course always have at least two custodes for cross-checking and backup purposes. (Which is the problem re Glassdoor and Yelp.)
- RcouF1uZ4gsC 3y ago
  Hacker News and Twitter

troupo 3y ago

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.

Mystery-Machine 3y ago
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...
- viraptor 3y ago
  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.
  - ben0x539 3y ago
    > 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?
    - viraptor 3y ago
      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.
- naikrovek 3y ago

brasic 3y ago

I miss the old status page: https://web.archive.org/web/20170110044141/https://status.github.com/ https://web.archive.org/web/20170110044141/https://status.gi...

sotrue922 3y ago

[dead]