logoalt Hacker News

chilmersyesterday at 7:04 PM3 repliesview on HN

The graph is not accurate, because GitHub's historical downtime data is not accurate.

For example, here is a Hacker News story about GitHub being down on July 28th 2016: https://news.ycombinator.com/item?id=12178449

Here's GitHub's historical uptime graph (on which this chart is based), saying there was no recorded downtime that day, or in fact that entire month: https://www.githubstatus.com/uptime?page=40


Replies

abrahamyesterday at 11:25 PM

GitHub launched a new status page Dec 2018[1]. It doesn't appear as if any history before Oct 2018 was ported over.

[1] https://github.blog/engineering/infrastructure/introducing-t... [2] https://web.archive.org/web/20181211191456/https://www.githu...

starkparkeryesterday at 11:37 PM

That graph has bugged me since it went viral. The methodology is horseshit: https://github.com/DaMrNelson/github-historical-uptime

Just dumping HARs from devtools from a status site that hallucinates 100% uptime when it has no data. For example, all GitHub services had 100% uptime in June 1996: https://www.githubstatus.com/uptime?page=200

The graph gives GitHub Actions 100% uptime before it launched to GA in November 2019. That factors into the average uptime for every month on the graph before that. It's fully horseshit.

antiframeyesterday at 8:20 PM

Looks like it's not accurate by under repporting not over reporting. So their down time was likely worse!

show 2 replies