How do they not have a single update in over 1.5 hours? This is ridiculous.
GitHub was down again
21–30 of 125 posts
Re: GitHub was down again
#22Why is outage history pre-acquisition removed from their history? If you try to go back in time it seems they only retain history up to a couple months after the acquisition. Is this just a 2 year retention policy or something being swept under the rug?
I have never worked at Github or MS and have no inside info on this, but it may be as simple as having switched to a MS-run system for outage history tracking as part of their own M&A integration.
Re: GitHub was down again
#23GitHub used to have a pretty cool status page, with all kinds of real time graphs. Does anyone know what happened to it? Since it makes me really sad that this status page is a plain lie, I had to visit HN to get the confirmation that they are having issues again, and that it just wasn't only me.
I read an article about it, look for "status page evolution" https://nimbleindustries.io/2020/06/04/has-github-been-down-...
From the first two graphs it looks like they are a lot less liberal about using "down" instead of "warn".
Re: GitHub was down again
#24Don’t host yourself, it’s impossible to meet the reliability of the professionals
Re: GitHub was down again
#25Why is outage history pre-acquisition removed from their history? If you try to go back in time it seems they only retain history up to a couple months after the acquisition. Is this just a 2 year retention policy or something being swept under the rug?
This change must have happened this year. I remember comparing pre and post acquisition outage rates a few months ago.
If it is not purposefully being swept under the rug, it sure is convenient.
Re: GitHub was down again
#26I was seeing PRs failing to update & webhooks failing to trigger upon pushing code for 30 minutes before GH's status page acknowledged anything. I'm surprised they don't have monitoring in place that would catch webhooks failing within minutes of the failure beginning.
At large bureaucratic organisations there's often political implications of changing the official status, so often it lags behind reality until it cannot be swept under the rug anymore Not saying it's right, just an observation
As a CTO responsible for an often failing eCommerce website that lost millions when down and which I took over, I fell in the same trap of trying to sweep things under the rug.
Until I decided to no longer do that and my life improved considerably.
Re: GitHub was down again
#27Why is outage history pre-acquisition removed from their history? If you try to go back in time it seems they only retain history up to a couple months after the acquisition. Is this just a 2 year retention policy or something being swept under the rug?
I think it's also worth noting that also corresponds with the Actions feature (went GA 11/11/19)
Re: GitHub was down again
#28Don’t host yourself, it’s impossible to meet the reliability of the professionals
No, it's not. Apart from scheduled downtime when nobody's using it (e.g. restarts in the morning to update the kernel), it's not that hard to beat GitHub's uptime for a small Gitea instance. My power's on more than GitHub is up.
A UPS and a tethered smartphone would get me three nines uptime-while-anyone-needs-it, which is well in excess of what I need.
Re: GitHub was down again
#29Why is outage history pre-acquisition removed from their history? If you try to go back in time it seems they only retain history up to a couple months after the acquisition. Is this just a 2 year retention policy or something being swept under the rug?
I can go back all the way to 2010: https://imgur.com/DsSKcFV
Re: GitHub was down again
#30It's been having issues all day. Wanted to show a coworker some changes I was proposing but the site wouldn't show the changes I'd pushed to my pull request. Ended up just having him pull the changes. FWIW the git backend always seems rock solid in comparison to the front end they have displaying it.
I'm not sure this time. I had a PR update and kick off a build half an hour or so ago, only to see the build fail because git couldn't parse what it got from the clone operation.