What has changed at GitHub to cause this?
https://www.forbes.com/sites/bernardmarr/2025/07/08/microsof...
111–120 of 214 posts
What has changed at GitHub to cause this?
https://www.forbes.com/sites/bernardmarr/2025/07/08/microsof...
Earlier quoted context omitted.
I once worked at a place with more micro services than engineers. We joked about "we have as many 8s of uptime as you need!"
> I once worked at a place with more micro services than engineers. Currently consulting somwhere with 30 services per engineer. I cannot convince them this is hell. Maybe that makes it my personal hell.
In that every night you're playing murder mystery, and its never fun.
Down? No sir we are not down. There are elevated error rates and degraded performance.
FTFY. (I've read AWS word it like that)
Man, a while ago I thought: "It happens often, alright, but every 2 weeks? Sounds like a slight exaggeration." But it really is every 2 weeks, isn't it? If I imagine in a previous job anything production being down every 2 weeks ... phew, would have had to have a few hard talks and course corrections.
Another site was constantly getting DDoS by Russians who were made we took down their scams on forums, that had to go through verisign back then, not sure who they're using now. They may have enough aggregate pipe it doesn't matter at this point
The worst part of all this is that GitHub's CTO and VP of Engineering sent out the usual "here's what we'll do to fix things" letter to their larger customers and, without exaggeration, it boiled down to: 1) "Here's a bunch of stuff we already did!" which... clearly isn't working, and 2) "We're continuing our Azure migration." also clearly not working. So needless to say, if you depend on GitHub for critical business…
Is "migrating to Azure" the new "migrating to SAP?"
Earlier quoted context omitted.
> I once worked at a place with more micro services than engineers. Currently consulting somwhere with 30 services per engineer. I cannot convince them this is hell. Maybe that makes it my personal hell.
Oooof that's rough. One strategy to convince is to get someone less technical than you to sit by you while you try and trace everything from one error'd HTTP request from start to finish to diagnose the problem. If they see it takes half a day to check every call to every internal endpoint to 100% satisfy a particular request sometimes that can help. Also sometimes they just think "this is a bunch of nerd stuff, why…
The real solution is probably to leave, but the market sucks at the moment. At least AI makes the 10-repos-per-tiny-feature thing easier.
It's starting to really look like the AI effect. It might be coincidence but I've noticed a lot more downtime and bad software lately. The last Nvidia drivers gave me a blue screen (last week or so), and speaking about Windows, I froze updates last year because it was clear they were introducing a bunch of issues with every update (not to mention unwanted features). I like AI but actually not for coding because code…
I think maybe it's not that GitHub is using AI, but that the amount of AI slop going into GitHub may be more than they expected.
Fuck sake. Again? Sorry, I realise this comment isn't up to HN's usual standards for thoughtfulness and it is perhaps a bit inflammatory but... look, I'd bet the majority of us on this site rely on GitHub and I can't be the only one becoming incredibly frustrated with its recent unreliability[0]? (And, yes, I did enough basic data analysis to confirm that it IS indeed getting worse versus a year, two years, and three…
> I realise this comment isn't up to HN's usual standards for thoughtfulness > And, yes, I did enough basic data analysis to confirm Perhaps you'd consider showing us that analysis? That sounds like it would make a pretty substantive, thoughtful comment.
Gaze upon the tapestry in which github paints it's failure with a thin copper red thread: