To be fair, before the aquisition, GitHub was super stable, but also it felt like they rarely changed or added anything.

After Microsoft acquired them, they started rolling out new features at an incredible pace. And if you look at the breakdown of the downtime, most of the downtime is in features that didn't exist before the acquisition.

Though not all of the downtime is in new features. The core is also less stable than ever.

In all fairness, the features expanded substantially after the acquisition so there's are a lot more components that can experience downtime. Pre-acquisition, github was a fairly simple code repository with issues bolted on. Actions, Dependabot, Codespaces, Advanced Security, Package Registry, Copilot, etc. all came after the acquisition and probably involve much more overhead than what github was prior to the acquisition. It basically went from code hosting platform where machines are sitting idle when pushes and pulls aren't happening to a fully integrated developer ecosystem. Any one of those things experiencing degraded performance is going to show up on an uptime chart.

Note that most of the downtime in that graph comes from Github Actions, which simply didn't exist before the Microsoft acquisition.

The downtime also starts happening in 2020, which is a while after the acquisition. 2020 was the year many people started learning to code while being stuck at home.

I’ve noticed the same thing with computers, whenever I install MS windows on them uptime tanks ;)

Microsoft acquiring GitHub is not a valid root cause analysis explaining Github’s degraded SLA.

On the other hand I think usage increased and GitHub operates now at a different scale.

Microsoft acquires GitHub and subsequently moves all infrastructure to Azure

No one hates msft more than me, but there’s no way you think this one data point is useful to explain anything at all