Top
Best
New

Posted by MattIPv4 9 hours ago

GitHub is once again down(www.githubstatus.com)
351 points | 185 commentspage 3
steeleduncan 9 hours ago|
What has changed at GitHub to cause this?
smartmic 9 hours ago||
AIpocalypse. Eaten too much Copilot dog food.
bartread 9 hours ago|||
Perhaps even AIslopalypse.
KaiserPro 8 hours ago|||
Looking at the status, its not one long outage, but lots of little ones, microslops if you will.
zahlman 8 hours 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 8 hours 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.

adzm 8 hours ago|||
Weird Al needs to capitalize on this whole AI/Al thing
pixelesque 9 hours 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 8 hours ago||
Perhaps staff cuts having longtails? https://www.itpro.com/software/microsoft/microsoft-layoffs-h...
pera 8 hours ago|||
Microsoft Makes AI Mandatory For Employees

https://www.forbes.com/sites/bernardmarr/2025/07/08/microsof...

voidfunc 9 hours ago|||
Azure
altairprime 9 hours 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

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 6 hours 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 9 hours ago|||
Vibe coding features.
staticassertion 9 hours 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 9 hours ago||
You never go full Azure
qudat 9 hours ago|||
Their primary goal in the last year was to move to Azure. Any massive infra migration is going to cause issues.
seneca 9 hours 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.

the_real_cher 9 hours ago|||
A.I. but that acronym can mean a number of things.

Artificial intelligence, Azure integration, many other things.

paxys 9 hours ago||
Senior engineers/leaders getting tired of Microsoft's shit and leaving.
rileymichael 9 hours ago||
looking forward to the `addressing-githubs-recent-availability-issues-3` news post
overgard 9 hours ago||
I remember back in the early Windows XP era when things got so bad that Microsoft basically had to make a hard pivot towards security and reliability.

I think they may need to do that once again. Almost every product of theirs feels like a dumpster fire. GitHub is down constantly, Windows 11 is a nightmare and instead of patching things they're adding stupid features nobody asked for. I think they need to stop and really look closely at what they're prioritizing.

tholford 8 hours ago||
Setting up a Gitea instance is approachable, especially with agent assistance.

https://about.gitea.com/

wenbin 8 hours ago||
I guess vibe coding can't solve such problem for now...
0xbadcafebee 7 hours ago||
I'm surprised nobody has tried to throw together a commercial alternative to GitHub. 50% of it is available as FOSS, the other 50% you can vibecode in a month (you can vibecode reliably, Microsoft/Google just suck at it). Afaict, reason we all keep using GitHub is it has a million features and isn't as ugly, difficult and slow as GitLab. (sorry GitLab, I love your handbook, hate your UX)
ekropotin 9 hours ago||
Remember when GitHub was cool? Pepperidge Farm remembers.
whalesalad 9 hours ago|
I remember. My GitHub user ID is #5907, account created 2008-04-08T20:27:36Z. I think it is inevitable that all good things come to an end, but it's still a bummer to see.
Freedom2 8 hours ago||
As do I. Mine is even earlier as well!
pylua 9 hours ago||
Anyone else notice other Microsoft cloud services ( for instance inside azure ) with bad performance also?

I can’t be specific but we are constantly complaining.

keithnz 9 hours ago||
No? Azures been rock solid for us.
pylua 8 hours ago||
Front door did have a major outage last year.
sysworld 8 hours ago||
The Azure management UI, yes, so slowww. But the services (VMs etc) have been good.
gverrilla 6 hours ago||
What's the successor?
swed420 6 hours ago||
https://radicle.xyz/
nichos 3 hours ago||
Forgejo
jiveturkey 2 hours ago|
I sure hope they created a restore point first.
More comments...