GitHub says sorry and vows to do better as uptime slips and devs complain Microsoft's code hosting shack Github has published a lengthy mea culpa about its availability and reliability woes - one that includes the words "we are sorry." outage GitHub appears to be struggling with measly three nines availability READ MORE Developers using the service have faced repeated downtime, and the apology …
All the smart people jumped ship from GitHub as soon as Microslop took it over.
It doesn't take a genius to predict that they would ruin the site with unwanted integrations and tools that nobody had asked for. That they can't even keep availability up at 99.9% is a terrible reflection on them.
...Since the second half of December 2025, agentic development workflows have accelerated sharply.
As per the article.
So they're admitting they did this to themselves, and that the tools they're using aren't up to the job. So... Stop using them please? ...and stop trying to force us to use them while they're at it?
That's not what they're admitting, though it's not totally clear unless you go read the original blog post.
They're not saying the problems are caused by *GitHub* making "a rapid change in how software is being built". They're saying the problems are caused by *other people* doing that, and slapping the results on GitHub. There are some pretty gnarly graphs in the blog post showing the massive acceleration in repo, commit and PR creation.
I think anyone who's trying to be a sysadmin in the current age could sympathize to a degree, TBF. Just trying to keep a simple web service up under the weight of scraper spam is a challenge. I would not be particularly keen to volunteer to run an open-access git forge right now. (Of course, they did volunteer for the job, and their parent company is one of the primary drivers of AI hype, soooo.)
Microslop had certainly been investing heavily around GitHub. Specifically in nailing copilot buttons to anything that works. Today pull requests are down - literally the reason to use GitHub. They even transferred it to their Copilot division. Blaming external use of LLM autocoders is disingenuous at best.
Has there yet been an existing entity which Microsoft has later involved itself in that wasn't subjected to the infusion of unwanted functionality and a significant reduction in reliability? Winding back through memory, all the way to windows 3.11 days, I cannot think of a single instance where an existing service has improved by any measure post MS involvement..
As long as MS, Azure, and Github consider vibe coding to be their primary tool things will just continue to get worse.
Every six months or so they come out and say 'oh wow, yeah that's bad, we sucked, our bad, we are TOTALLY committed to fixing it now.' And then it just get worse.
Why? Because the only thing they actually care about is shovelling their 'AI' shit, and it turns out unloading sewage trucks on top of Github does not help it get better.
I moved my stuff off Github to Gitlab. It was tedious but straightforward. There's no excuse other than organizational inertia, and maybe that all your IT people are now morons who can't do anything without Copilot, which would certainly bungle the transition.
