abadideaNINETY DAYS
NINETY INCIDENTS
NINETY PERCENT
YOU PAID FOR ALL FIVE NINES BUT YOU’LL ONLY NEED THE EDGE
slembcke@0xabad1dea Where did this come from? status.github.com paints a very different picture, though also not particularly great honestly…
@slembcke to confirm what someone else said while I was asleep, it’s an independent third party tracker called the “missing” github status page. https://mrshu.github.io/github-statuses/
they track ten subsystems separately, which are each in the 96% to 99.9% range, then overlay all those incidents on the same timeline to arrive at 90% overall.
I do not have any particular stance on whether github’s own tracker or this third party one is more fair and accurate, beyond “90-90-90 is hilarious” and observing only one of them has a contractual stake in possibly sometimes downplaying issues a little bit.
gunstick@0xabad1dea @slembcke if each subsystem is crucial for github to work, you multiply those uptimes and get 90.
If the subsystems are independent then can't do that.
If the CI system is down, you can't say github is down.
I would then merge the timelines and get some metric "how long has there been no issue at all".
That can be very low and the website is still fine.
If the subsystems are independent then can't do that.
If the CI system is down, you can't say github is down.
I would then merge the timelines and get some metric "how long has there been no issue at all".
That can be very low and the website is still fine.