[scribu]

It's easy to see from the uptime history [1] that there have been many more incidents in April-June than in January-April.

Don't know if that has anything to do with the Microsoft acquisition, but it is concerning.

[1] https://www.githubstatus.com/uptime?page=1

[esperent]

They're still averaging 99.81% up-time over the last three months. This means they have been down for a total of 4 hours out of 90 days. I don't think it's all that concerning.

[jillesvangurp]

The gold standard here is 5 9s, not 2.

They have paying customers that are being inconvenienced by this. We lost time over this multiple times in the last few weeks.

So, not good. IMHO they are having some major issues with their release process that they need to address. Standards have slipped there; they used to be better at this.

[robertlagrant]

The numbers on Github Enterprise might be different. They probably roll out changes to the free/$4 per month Github first.

[z9e]

My company has GH enterprise and these numbers look accurate based on my experience. We’ve noticed a lot of downtime that has impacted us.

[shaklee3]

Isn't enterprise the self-hosted solution?

[ilikehurdles]

I believe Enterprise has a self-hosted option, and you can have Enterprise without the self-hosting.

[trm42]

This kind of depends whether you have something urgent work to handle through Github. Been waiting for over an hour so I could continue my work but Github PR-functionality hasn't shown latest changes because of the currently happening outage so I cannot. Really, really annoying and wastes partially my planned work for the day.

(of course I'm working on other stuff in the meantime but splices focus unnecessarily)

[rattray]

Wow, that's stark. I count 6 in April-June (2 major outages) and only 1 in January-March (0 major outages.

I wonder if COVID has affected this somehow. Anecdotally I've heard of at least one other ~peer company with a large rise in incidents/outages since April.

Strange since both companies previously had a strong culture of remote work (maybe 1/4 to 1/3 of eng was remote) going into the pandemic, so I'd be quite surprised if all-WFH contributed somehow...

[rb12345]

If GitHub's been migrating to Azure infrastructure on the backend, it's possible that everyone else moving to all-WfH helped to cause it. Teams use massively increased during lockdown for obvious reasons and that's definitely Azure-based. If Teams managed to overload Azure capacity, I could see that having knock-on effects on GitHub.

[robertlagrant]

> it's possible that everyone else moving to all-WfH helped to cause it

No, MS prioritising Teams land grabbery is what caused it.

[rattray]

The other company does not use Azure.

[ksec]

I remember there were a few incident with AWS taking down the whole internet, Verizon BGP incident, and a few others that is completely not the fault of Github. I wonder if those were included or affected.

And generally speaking Github has been 100x more active post Microsoft acquisition. So I am not surprised at the downtime.

And I will gladly trade another few hours if not more downtime if they could just rollback the side panel design.