Elektrine lite

← Feed

@ironicbadger@techhub.social

Post #873533

2026-03-31 22:31 UTC

Brutal. When Microsoft acquired GitHub.

Replies (28)

  • @xethos@mastodon.xethos.net 2026-04-01 07:33

    @ironicbadger@techhub.social My favourite part is only hitting 100.0% uptime during winter break, when nobody is around to actively break it

    Open ##878057

  • @Tubsta@soc.feditime.com 2026-03-31 22:39

    @ironicbadger and still no #IPv6

    Open ##1080762

  • @jmelesky@tinylad.social 2026-04-01 01:53

    @ironicbadger Geez, this is like what happened when they first tried to convert Hotmail to run on Windows servers.

    Open ##1080763

  • @Nimbius666@comp.lain.la 2026-04-01 01:55

    @ironicbadger no fair. Oracle would have done it much faster but Redmond beat them to it :/

    Open ##1080764

  • @mc@toot.houbahouba.de 2026-03-31 22:32

    @ironicbadger lessons learned? stay away from VC...grow organically and listen/follow your users demands ;)

    Open ##1201118

  • @theorangetheme@en.osm.town 2026-03-31 22:52

    @ironicbadger Woof.

    Open ##1201148

  • @cap_ybarra@beige.party 2026-03-31 23:10

    @ironicbadger as a post msft acquisition survivor this tracks

    Open ##1201149

  • @Arapalla@aus.social 2026-04-01 01:10

    @ironicbadger Closing it down and rolling its subscribers to MS products in 8 7 6 5 4

    Open ##1201157

  • @Amgine@mamot.fr 2026-04-01 01:11

    @ironicbadger Azure.

    Open ##1201159

  • @ironicbadger #Alt4You 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.

    Open ##1201174

  • @itgrrl@infosec.exchange 2026-04-01 02:06

    @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)

    Open ##1201179

  • @ironicbadger Why settle for Five Nines of reliability when you can get Nine Fives?

    Open ##1201180

  • @justbob@kolektiva.social 2026-04-01 02:16

    @ironicbadger That is the least of the problems with it, got that damn AI stealing everyones hard work

    Open ##1201201

  • @andymckay@mastodon.social 2026-04-01 02:29

    @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.

    Open ##1201202

  • @OrionKidder@mas.to 2026-04-01 02:30

    @ironicbadger Acquire and ruin. This is the corporate way.

    Open ##1201229

  • @ironicbadger Where was this chart published?

    Open ##1201230

  • @llewelly@sauropods.win 2026-04-01 03:49

    @ironicbadger behold the jagged teeth of the dog that eat all the dogfood!

    Open ##1201237

  • @Jourei@mas.to 2026-04-01 03:50

    @ironicbadger Could anyone explain to me, how is this possible? I would imagine they would keep things running on the original hardware etc. which I wouldn't expect to fluctuate like this.

    Open ##1201238

  • @thunfisch@chaos.social 2026-04-01 04:28

    @ironicbadger @isotopp what’s the data source behind it? Official status page? Because that has been notoriously inaccurate long before microslop took over.

    Open ##1201246

  • @ironicbadger The inverse Midas touch

    Open ##1201251

  • @ironicbadger searching for "github downtime 2016" I don't trust the old values

    Open ##1201278

  • @simonwaight@mastodon.online 2026-04-01 05:23

    @ironicbadger interested if you can map that to growth/shrinkage in users and/or volume or data being used.

    Open ##1201281

  • @luceos@fosstodon.org 2026-04-01 05:37

    @ironicbadger wait, they went from 100% uptime on their own servers,which were constantly on, to 99,5% as lowest uptime on a scalable infrastructure? That's 3,5 hours max spread over a month. And you're taking the piss on them for that? That's wild. Maybe focus on their link to Israel in the Gaza war or something.

    Open ##1201282

  • @follpvosten@karp.lol 2026-04-01 05:55

    @ironicbadger@techhub.social lmao yeah that checks out

    Open ##3001998

  • @zetasyanthis@dragon.style 2026-04-01 05:55

    @ironicbadger@techhub.social And this is why we keep local repo copies for production repos. :)

    Open ##3001999

  • @ironicbadger@techhub.social Microsoft has always had a peculiar reverse Mida's touch, transforming into junk everything they touch - remember Zune, Windows Phone, etc.

    Open ##3002000

  • @coldclimate@hachyderm.io 2026-04-01 06:35

    @ironicbadger@techhub.social is that because people left, or tech investments stopped, or something like bits of housing were moved to azure?

    Open ##3002003

  • @comsey@mstdn.social 2026-04-01 07:04

    @ironicbadger@techhub.social I expect them to start measure the SLA properly after the acquisition - such a change looks rather than a change of methodology rather than immediate effect of a merge (fuck Microsoft anyway, but not for that)

    Open ##3002005