Brutal.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Woof.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger as a post msft acquisition survivor this tracks
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Looks about right. I switched to Codeburg, personal Forgejo behind TS, and VScodium. Couldn’t be happier.
-
Brutal.
When Microsoft acquired GitHub.
Azure.
-
Brutal.
When Microsoft acquired GitHub.
A graph demonstrating that the GitHub website's uptime suffered considerably after being acquired by Microsoft.
The graph shows average uptime of the website by-month from April 2016 to January 2026. Months that earn 100% are colored green, while months that miss that goal are colored either red or yellow, depending on some undisclosed metric of severity.
A line is marked in November 2018 where Microsoft acquired GitHub. Before that, no months were visibly worse than 100%. There's one red dot, but it's not visibly different otherwise. For the first year after the acquisition uptime is worse but acceptable, and stays above 99.95%: six out of 12 months earn 100%.
After October 2019 the story flips completely. Only one month has earned 100% uptime since then, and the remaining months vary wildly from 99.98% to about 99.70%. May 2023 was the worst, crashing almost as low as 99.5% uptime.
Honestly, it looks like a seismograph that's started recording an active earthquake.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger@techhub.social Geez, this is like what happened when they first tried to convert Hotmail to run on Windows servers.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger no fair. Oracle would have done it much faster but Redmond beat them to it
-
A graph demonstrating that the GitHub website's uptime suffered considerably after being acquired by Microsoft.
The graph shows average uptime of the website by-month from April 2016 to January 2026. Months that earn 100% are colored green, while months that miss that goal are colored either red or yellow, depending on some undisclosed metric of severity.
A line is marked in November 2018 where Microsoft acquired GitHub. Before that, no months were visibly worse than 100%. There's one red dot, but it's not visibly different otherwise. For the first year after the acquisition uptime is worse but acceptable, and stays above 99.95%: six out of 12 months earn 100%.
After October 2019 the story flips completely. Only one month has earned 100% uptime since then, and the remaining months vary wildly from 99.98% to about 99.70%. May 2023 was the worst, crashing almost as low as 99.5% uptime.
Honestly, it looks like a seismograph that's started recording an active earthquake.
@AcornSquashbuckler @ironicbadger When did they Rewrite It In React?
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger big oof (for smallish values of oof) but I’d also like to see that graphed against active usage volume to get the full picture
(yes, regardless, a “hyperscaler” should be able to handle the volume)
-
Brutal.
When Microsoft acquired GitHub.
Why settle for Five Nines of reliability when you can get Nine Fives?
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger hmm, quite a few opinions on that chart
tl;dr it’s complicated.Most of GitHub services, until I left a couple of years ago were not on Azure.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Acquire and ruin. This is the corporate way.
-
Why settle for Five Nines of reliability when you can get Nine Fives?
@DaveMWilburn @ironicbadger get the sweet 55.5555555% availability
-
R relay@relay.mycrowd.ca shared this topic
-
@ironicbadger as a post msft acquisition survivor this tracks
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Just like when they bought Hotmail back in the day.
-
Brutal.
When Microsoft acquired GitHub.
@ironicbadger Where was this chart published?
-
@ironicbadger hmm, quite a few opinions on that chart
tl;dr it’s complicated.Most of GitHub services, until I left a couple of years ago were not on Azure.
@andymckay @ironicbadger what's complicated about it? it used to be good and now it's bad
-
@ironicbadger Where was this chart published?
@a_different_jlh https://damrnelson.github.io/github-historical-uptime/
Sorry I should have linked to the source
-
@andymckay @ironicbadger what's complicated about it? it used to be good and now it's bad
@aburka @ironicbadger ah I was replying to a different post about it being Azure or Azure management. I did Mastodon wrong, sorry.
I will say after the acquisition when GitHub became rapidly more complex as features were added, the definition of downtime requiring a status change became a lot more strict and focused (for some teams). A bit more loose and easy beforehand.
-
@aburka @ironicbadger ah I was replying to a different post about it being Azure or Azure management. I did Mastodon wrong, sorry.
I will say after the acquisition when GitHub became rapidly more complex as features were added, the definition of downtime requiring a status change became a lot more strict and focused (for some teams). A bit more loose and easy beforehand.
@andymckay @ironicbadger yeah I can believe there are many causes, mismanagement and forced development speed as much as technology changes
