5 ms·

What has changed at GitHub to cause this?

by steeleduncan 6mo ago

smartmic 6mo ago
AIpocalypse. Eaten too much Copilot dog food.
- bartread 6mo ago
  Perhaps even AIslopalypse.
  - zahlman 6mo ago
    I've been using "slopocalypse". People already know AI is responsible, but slop existed before — e.g. conventionally generated SEO spam. It's just... so much worse now.
    - bartread 6mo ago
      "Slopocalypse": yeah, I like that. Easier to pronounce too. At any rate, it seems like GitHub is back up now, so we'll see how long that lasts.
  - KaiserPro 6mo ago
    Looking at the status, its not one long outage, but lots of little ones, microslops if you will.
- adzm 6mo ago
  Weird Al needs to capitalize on this whole AI/Al thing
voidfunc 6mo ago
Azure
- altairprime 6mo ago
  > Azure To explain this one-word comment for those unfamiliar, see previously: GitHub will prioritize migrating to Azure over feature development (5 months ago) https://news.ycombinator.com/item?id=45517173 https://news.ycombinator.com/item?id=45517173 In particular: > GitHub has recently seen more outages, in part because its central data center in Virginia is indeed resource-constrained and running into scaling issues. AI agents are part of the problem here. But it’s our understanding that some GitHub employees are concerned about this migration because GitHub’s MySQL clusters, which form the backbone of the service and run on bare metal servers, won’t easily make the move to Azure and lead to even more outages going forward.
  - 0xbadcafebee 6mo ago
    Age-old lesson: change the tires on the moving vehicle that is your business when it's a Geo Metro, not when it's a freight train. I'm sure the people with the purse strings didn't care, though, and just wanted to funnel the GH userbase into Azure until the wheels fell off, then write off the BU. Bought for $7.5B, it used to make $250M, but now makes $2B, so they could offload it make a profit. I wonder who'll buy it. Prob Google, Amazon, IBM, Oracle, or a hedge fund. They could choose not to sell it, but it'll end up a writeoff if the userbase jumps ship.
yoyohello13 6mo ago
Vibe coding features.
qudat 6mo ago
Their primary goal in the last year was to move to Azure. Any massive infra migration is going to cause issues.
- seneca 6mo ago
  > Any massive infra migration is going to cause issues. What? No, no it's not. The entire discipline of Infrastructure and Systems engineering are dedicated to doing these sorts of things. There are well-worn paths to making stable changes. I've done a dozen massive infrastructure migrations, some at companies bigger than Github, and I've never once come close to this sort of instability. This is a botched infrastructure migration, onto a frankly inferior platform, not something that just happens to everyone.
pixelesque 6mo ago
Possibly a combination of moving infrastructure to Azure, and also a significant increase in the number of PRs and commits due to Vibe-coding?
- cyanydeez 6mo ago
  Perhaps staff cuts having longtails? https://www.itpro.com/software/microsoft/microsoft-layoffs-hit-azure-cloud-division-in-latest-round-of-cuts https://www.itpro.com/software/microsoft/microsoft-layoffs-h...
- jamiemallers 6mo ago
  [dead]
deleted 6mo ago
[deleted]
paxys 6mo ago
Senior engineers/leaders getting tired of Microsoft's shit and leaving.
staticassertion 6mo ago
I assume this is all of the pains of going from "GHA is sorta kinda on Azure", which was a bad state, to "GHA is going full Azure", which is a painful state to get to but presumably simplifies things.
- dec0dedab0de 6mo ago
  You never go full Azure
the_real_cher 6mo ago
A.I. but that acronym can mean a number of things. Artificial intelligence, Azure integration, many other things.
pera 6mo ago
Microsoft Makes AI Mandatory For Employees https://www.forbes.com/sites/bernardmarr/2025/07/08/microsoft-makes-ai-mandatory-for-employees-what-it-means-for-your-career/ https://www.forbes.com/sites/bernardmarr/2025/07/08/microsof...

What has changed at GitHub to cause this?

smartmic 6mo ago

AIpocalypse. Eaten too much Copilot dog food.

bartread 6mo ago
Perhaps even AIslopalypse.
- zahlman 6mo ago
  I've been using "slopocalypse". People already know AI is responsible, but slop existed before — e.g. conventionally generated SEO spam. It's just... so much worse now.
  - bartread 6mo ago
    "Slopocalypse": yeah, I like that. Easier to pronounce too. At any rate, it seems like GitHub is back up now, so we'll see how long that lasts.
- KaiserPro 6mo ago
  Looking at the status, its not one long outage, but lots of little ones, microslops if you will.
adzm 6mo ago
Weird Al needs to capitalize on this whole AI/Al thing

voidfunc 6mo ago

Azure

altairprime 6mo ago
> Azure To explain this one-word comment for those unfamiliar, see previously: GitHub will prioritize migrating to Azure over feature development (5 months ago) https://news.ycombinator.com/item?id=45517173 https://news.ycombinator.com/item?id=45517173 In particular: > GitHub has recently seen more outages, in part because its central data center in Virginia is indeed resource-constrained and running into scaling issues. AI agents are part of the problem here. But it’s our understanding that some GitHub employees are concerned about this migration because GitHub’s MySQL clusters, which form the backbone of the service and run on bare metal servers, won’t easily make the move to Azure and lead to even more outages going forward.
- 0xbadcafebee 6mo ago
  Age-old lesson: change the tires on the moving vehicle that is your business when it's a Geo Metro, not when it's a freight train. I'm sure the people with the purse strings didn't care, though, and just wanted to funnel the GH userbase into Azure until the wheels fell off, then write off the BU. Bought for $7.5B, it used to make $250M, but now makes $2B, so they could offload it make a profit. I wonder who'll buy it. Prob Google, Amazon, IBM, Oracle, or a hedge fund. They could choose not to sell it, but it'll end up a writeoff if the userbase jumps ship.

yoyohello13 6mo ago

Vibe coding features.

qudat 6mo ago

Their primary goal in the last year was to move to Azure. Any massive infra migration is going to cause issues.

seneca 6mo ago
> Any massive infra migration is going to cause issues. What? No, no it's not. The entire discipline of Infrastructure and Systems engineering are dedicated to doing these sorts of things. There are well-worn paths to making stable changes. I've done a dozen massive infrastructure migrations, some at companies bigger than Github, and I've never once come close to this sort of instability. This is a botched infrastructure migration, onto a frankly inferior platform, not something that just happens to everyone.

pixelesque 6mo ago

Possibly a combination of moving infrastructure to Azure, and also a significant increase in the number of PRs and commits due to Vibe-coding?

cyanydeez 6mo ago
Perhaps staff cuts having longtails? https://www.itpro.com/software/microsoft/microsoft-layoffs-hit-azure-cloud-division-in-latest-round-of-cuts https://www.itpro.com/software/microsoft/microsoft-layoffs-h...
jamiemallers 6mo ago
[dead]

deleted 6mo ago

[deleted]

paxys 6mo ago

Senior engineers/leaders getting tired of Microsoft's shit and leaving.

staticassertion 6mo ago

I assume this is all of the pains of going from "GHA is sorta kinda on Azure", which was a bad state, to "GHA is going full Azure", which is a painful state to get to but presumably simplifies things.

dec0dedab0de 6mo ago
You never go full Azure

the_real_cher 6mo ago

A.I. but that acronym can mean a number of things. Artificial intelligence, Azure integration, many other things.

pera 6mo ago

Microsoft Makes AI Mandatory For Employees https://www.forbes.com/sites/bernardmarr/2025/07/08/microsoft-makes-ai-mandatory-for-employees-what-it-means-for-your-career/ https://www.forbes.com/sites/bernardmarr/2025/07/08/microsof...