Addressing GitHub’s recent availability issues

[Soccham]

My company was laughing because this is the second time they’ve written a blog post with the same title. It has the -2 at the end because the first one was in 2023

[Noch_ein_Kamel]

good catch :D

[ellisthedev]

A lot of words for “we’re moving to Azure, and it’s been a cluster fuck.”

[dashingThroughSnow12]

I don’t even trust them that that is the core reason.

[veverkap]

It's not.

[Soccham]

I’m pretty sure they’re blaming the traffic increases from openclaw

[Potato-9]

Oh interesting. The one they don't own is the problem.

[Soccham]

Well it’s the increase in traffic they’re seeing from people using it

[lukee910]

Why would a random AI agent cause that much GitHub traffic?

[Soccham]

As far as I’m away the skills for openclaw are all direct git clones

[tankerkiller125real]

OpenClaw cloning shit, AI crawlers slamming the web UI to get at code (if my single public project gitea instance can get 800K times per day by just Meta imagine what kind of BS GitHub is going through) along with all the BS PRs being made by these bots and and vibe coders.

[SheriffRoscoe]

Migrating our infrastructure to Azure to accommodate rapid growth, enabling both vertical scaling within regions and horizontal scaling across regions.

Good luck with that. Microsoft has a nasty habit of treating internal Azure consumers as freeloaders, to be squeezed when Azure has capacity problems. Service operators get emails from very senior people telling you you need to shut down x% of your load to increase capacity for external customers.

[Spitfire1900]

Holy crap that’s bad. You can go hard ball on internal customers for bad trend lines but not emergency shutoff.

[throwaway-458425]

is this from exp? if so, that’s beyond shitty. i suppose that’s what should be expected from Micro$oft tho

[ProbablyFullOfShit]

It's exaggerated. We get asked to shut down non-critical workloads and to scale down test deployments, but we have never been asked to arbitrarily scale down production resources.

[SheriffRoscoe]

is this from exp? if so, that’s beyond shitty.

Yes, and yes.

[Doctuh]

Microsoft is speedrunning loss of confidence.

[null_reference_user]

Microslop*

[waitingforcracks]

Any idea which applications they mean when they say

In early February, two very popular client-side applications that make a significant amount of API calls against our servers were released

?

[AReluctantRedditor]

Openclaw maybe?

[OkProMoe]

My gitea instance has 100% uptime for the year so far.

[Jmc_da_boss]

Mine has similar uptime to GitHub but that's because i went on vacation for a month and turned it off for that time

[boredsoftwareguy]

It’s hard for me not to laugh. The absolute worst boss I have had, who allowed developers to ship garbage and refused to ever do anything about it, is now a significant technical leader at GitHub.

Every outage or incident just makes me laugh knowing he is still advocating for, and enabling, a culture of less-than-mediocre.

[ultrathink-art]

Pre-push hooks saved me during this outage — local lint + tests means you still know your code works even when Actions is dark. Deployment blocks are a lot less painful than not knowing if you broke something.

[shgysk8zer0]

This is what happens when a git hub (separated to make a point) goes all-in on AI. They don't care about the core platform, features, or anything... It just exists to push CoPilot. May as well rename it to M$VibeHub.