Comment by maccard
18 hours ago
GitHub’s reliability issues started earlier than the boom in agentic coding they talk about. I have comments on here from 2025 talking about massive outages with actions and issues.
18 hours ago
GitHub’s reliability issues started earlier than the boom in agentic coding they talk about. I have comments on here from 2025 talking about massive outages with actions and issues.
When you're the uncontested market leader, you don't budget operations to be perfectly reliable, you budget to not be too unreliable. All those 9's are expensive after all.
The AI boom caught them napping though, and they're slipping well into the too unreliable category
> The AI boom caught them napping though
Microsoft, who invested eyewatering sums into AI, even near to betting the whole company on an AI boom, is surprised about the AI boom?
Microsoft bet everything on possible AGI, no one thought the result would be a bonafide commit printing machine.
2 replies →
Microsoft considers it a bonus if a hype lets one department cripple another department.
GitHub uptime is cyclical. It's bad because they won't focus on the core, and then the right users complain and GitHub focuses on core again before it repeats. This is just the latest round exacerbated by vibe coding
Another commenter replied, but was downvoted by angry employees of Microsoft for a fairly anodyne statement.
Microsoft management knows this. It's not like there haven't been attempts to solve these core problems. The issue is GitHub was built by exceptional engineers, and none of those people are still around.
I maintain all these problems began when they migrated off Erlang and egitd. :)
[dead]
It was related to their migration to Azure as far as I know
So they completed the migration? Didn't see that being reported.
I don’t know