I seriously believe that it's not that GitHub is run on AI-generated code that's responsible for these slew of outages recently. I think it's crumbling under the load of a significantly large amount of AI-enabled coding with users raising PRs and pushing content a lot more than previously.
Obviously, if this is true, the team at GitHub is failing to scale their infra to meet the workload demands.
No wonder they don't publish an availability percentage. If I was a business customer paying for GitHub I would be very upset with the availability lately.
Someone built an archive of Github statuses to show aggregate uptime, last month and this month Github's uptime is below 90%, not even one "nine" of availability: https://mrshu.github.io/github-statuses/
87% uptime for Github in February 2026. They've got to get it together.
Unless you're unemployed ATM, what is happening throughout corporate America is forcing employees to use LLM tools or get fired. It's hard to not see the connection, big tech offerings were already shit before but since all these mandates it's gotten noticeability worse.
You don't get to back away from the LLM damage when you were making the media rounds telling everyone to use these tools. This is a direct result of using these tools: decaying code, rotten services, and putrid responses.
GitHub itself was reorged under the CoreAI division recently, I think.
For the stability issues, I see it more as a potential tenuous link between having to hyper accelerate the Azure moves with a "you have no excuses because AI makes everything easier" sentiment from above, and then the more obvious literal situation of devs maybe vibecoding infra changes.
No evidence of the latter, just the likelihood, given the incentives.
Obviously, if this is true, the team at GitHub is failing to scale their infra to meet the workload demands.
reply