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 operations, you need to start thinking about what a world without GitHub looks like for your business and start working your way toward that. I know my confidence in GitHub's engineering leadership is at rock bottom.

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 quality is correlated to how well you understand the underlying systems you're building on, and AI is not really reasoning on this level at all. It's clearly synthesizing training data and it's useful in limited ways.

Took a full 8 years for a Microsoft acquisition to go to shit, which is probably a record. Kudos to the Github team for holding out this long.

Every day more Microsofty...they should rename to "Your Repository Needs To Restart To Apply Updates"

Down? No sir we are not down. There are elevated error rates and degraded performance.

I'm just going to stand by until Microsoft is back in everyone's good graces again by releasing some oss software that we all swoon over

I'm glad I moved over to forgejo. Being selfhosted, the UI loads faster. Most importantly, the thing is always responsive.

They invented the perfect solution to stop supply chain attacks.

Microslop at it again

github is at one nine, basically: https://news.ycombinator.com/item?id=47428035

Does anyone else ever think "that code I just pushed into my repo just took down all of github..." whenever it goes down around the same time you sync your changes?

Just moved a project of mine to Gitlab. Created this very simple component with codex that will keep a mirror updated on GitHub for me, so I can focus development on Gitlab.

https://gitlab.com/gabriel.chamon/ci-components/-/tree/main/...

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.

Do your part; remind people that Github is not git. Git is decentralizable and people should know this.

GH is ripe for a disruptor right now.

At this rate it will be a matter of time before a "Github is up" parody site reaches the top of HN

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)

And this is why I self host a lot of my Git stack with Gerrit...

Microslop

Hitting 500s when trying to push branches and create PRs.

Setting up a Gitea instance is approachable, especially with agent assistance.

https://about.gitea.com/

What has changed at GitHub to cause this?

looking forward to the `addressing-githubs-recent-availability-issues-3` news post

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.

I guess vibe coding can't solve such problem for now...

Remember when GitHub was cool? Pepperidge Farm remembers.

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.

That Go rewrite continues to rear its head, eh?

Moved to self hosted crowci instead of actions.

Would be easier for them to just tell us when it’s up these days

Can this downtime be quantified to actual monetary losses?

I've been sitting here waiting for a critical deploy to happen via GitHub Actions (I know, hour fault, we should have left ages ago). My patience for this bullshit is gone, I'm going to be pushing very hard to get us off of GitHub entirely except for public code mirrors going forward.

Edit: oh look, their site says all good, but I still have jobs stuck. What a pile of garbage.

I'm so sick of this.

Must be Tuesday then

So am I the only one thinking that maybe GitHub is succumbing to the weight of AI slop that's coming in from all the vibecoding, clawbots, and other AI workflows?

Github CEO must be on HN, right? If so, any comments?

They have not even bothered to implement entra login when they have their competitors login for years, do they even know what their product is? Or are you just a middle man for slop?

Microsoft products are so human, they stop working weekly as if they're observing some sort of sabbath ...

That's just like your Vibe man; can you just copilot your wayout of these problems?

Did MS finish the Hotmail transition?

Vibe check?

Does github not do any kind of blue/green rollouts or what

I'm going to blame Claude Code!

My vscode slop session stopped in between. Maybe it's for the better

At least it happened after I did my work for the day... jfc!

For fucks sake.

I've been considering it for a while, but I'm definitely now pitching a move away from GitHub at our organization.

h8 github so much. ahhhhhh

You have GOT to be kidding me.

GitHub goes down at least once a week as I said before. [0] thanks to Copilot, Tay.ai and Zoe chatbots wrecking the platform instead of humans maintaining it.

If there was a prediction market for when GitHub experiences an outage every week, then you would make a lot of money.

[0] https://news.ycombinator.com/item?id=47487881

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 years ago, and is particularly bad since the start of this year.)

[0] EDIT: clearly not from looking at the rest of the comments in this discussion.

Why don't companies with chronic outages mimic their stack from top to bottom (i.e. starting with a new domain), then before making a change, make the change on the duplicate stack and blast it with mock requests.

Might catch 90% of problems before they make it into the real stack?

E.g. every step of GitHub's migration to Azure could be mimicked on the duplicate stack before it's implemented on the primary stack. Is this just considered too much work? (I doubt cost would be the issue, because even if it costs millions, it would pay for itself in reduced reputational damage from outages).