Live data from Hacker News

Incident with Github.com [resolved]

githubstatus.com

401–410 of 1001 posts

Re: Incident with Github.com [resolved]

#401

To everyone who is angry: calm down. Github’s servers are constantly on fire as their usage increased something like 50x due to LLM sloppers pushing large amounts of trash code Unless you have a emergency hotfix (you don’t), go hit the gym or walk outside. If a work tool going down triggers you enough mentally to start angrily ranting online, it’s a sign you need to chill out and focus more on your health

That's an overly optimistic view of things. For a lot of us GitHub is critical infrastructure, which if it goes down loses us and our customers money.

If its so critical why relying on it, and not having ie some mirror or some other way to handle any sort of outage like this. its not like Microsoft is your friend or good business partner, ever.

With every single of these enterprise 'cloud' offerings you are giving (almost) complete power over your business/project to somebody else who couldn't care less about your success or failure, you are simply irrelevant for them. I see it at work too, every time critical external systems go down whole bank stops still, just because few bucks were saved yearly on some on-prem servers.

Look at it this way, you are learning some important lesson today and finding great area of improvement for resiliency from now on.

Re: Incident with Github.com [resolved]

#402
post #99

This is starting to feel like Twitter. For a variety of reasons, we had a centralized place where everyone of a particular set of persuasions could connect, and this had outsize benefits for the community as a whole. That place is becoming untenable, and with the loss of goodwill and stability, the community’s started to dissipate. But there isn’t one obvious transition candidate, so the diaspora is finding itself sp…

> spread across a bunch of disparate places and services.

This is the way. Stop centralizing everything.

Re: Incident with Github.com [resolved]

#403
GitHub is down days of that week that end with day these days. If I were a paying customer I'd be cancelling soon. GitHub is sort of foundational at this point and when its down nearly every day of the week it cannot be foundational.

Re: Incident with Github.com [resolved]

#404

Earlier quoted context omitted.

Yes, but GitHub enterprise has different uptime ( https://us.githubstatus.com/posts/dashboard ) and actually does have an SLA. Edit: it seems GHE is also affected by the outage and isn't much better.

Since upgrading to Cloud Enterprise... why didn't my GH uptime get any better? Guess on-prem GHE server is the only way to do that.

My understanding is the us.githubstatus.com is only if you are using GitHub enterprise with a custom subdomain and data residency in the US because then *some* of the infrastructure is separate from GitHub.com.

Re: Incident with Github.com [resolved]

#406
post #76

Earlier quoted context omitted.

Copy/paste of a comment I posted a couple months ago: I am not trying to make any excuses for GitHub, however I recall one tweet that made my eyes bug-out: > Yup, platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.) > GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week i…

That's fine, but rate limiting is a solved problem at this point. They need to rate-limit free accounts and be realistic about their limits instead of letting the system fail.

They were about to push a big change to actions pricing a little wihle ago and people revolted

Re: Incident with Github.com [resolved]

#407

I don't understand why Github hasn't solved this problem with pricing updates. My understanding is they are getting hammered with LLM generated code growing their traffic by over an order of magnitude. So why not rate limit non-paying users and charge for whatever scarce resource is being consumed that is causing them to constantly fall-over? This seems like a basic economics problem.

Microsoft executives have an incentive to pretend that AI is great and scaling it has no problems

Re: Incident with Github.com [resolved]

#408

Earlier quoted context omitted.

It seems vastly higher on every region and VPN I've tested, so I think this is a case of the "technicalies". It is technically 20%, because a bunch of the requests that happen on page load do succeed. Just not the few crucial ones that are required for the page to load correctly - those return a 500 the vast supermajority of the time.

Feel free to disregard this because ultimately its a tangent that doesn't matter; but supermajority is specifically a political term referring to the required threshold to advance legislation when simple majority isn't procedurally enough. It doesn't mean simply a greater share of.a majority

This is how language evolves.

For supermajority: the construction means “beyond majority” or “above majority”, it is implemented as a higher percentage in most systems, and there is a utility in being able to refer to high ratio majority.

So people have repurposed a technical word to a general word, of roughly the same meaning.

Re: Incident with Github.com [resolved]

#409
post #29

I had a lot of goodwill for GitHub but I think today is the tipping point. Looking at a unicorn page, I feel this lingering hope that it's transient (like it usually was in the old days) but my mind reassures me it's probably going to be a long full outage again. The hope is dead.

I’m willing to give them a break as I’m assuming they have a lot of scaling problems due to the influx of LLM assisted coding. But maybe I’m wrong?

> scaling problems due to the influx of LLM assisted coding

You mean people pushing LLM assisted coding, or github's own coders pushing LLM assisted code to production ? :-).

I am more inclined to think that it is the second, but if the reason is the first, what is particular hard to scale ? It's not like everybody is vide-coding into a single repository, so I would expect that most of the load would naturally be scalable by increasing the resources. If for some reason that is not possible, I would expect a corporation as big as Github to keep the paying customers working by gracefully denying service to the free tier, not to collapse like an house of cards.

Re: Incident with Github.com [resolved]

#410

Earlier quoted context omitted.

That's an overly optimistic view of things. For a lot of us GitHub is critical infrastructure, which if it goes down loses us and our customers money.

How is github being down losing you guys money?

Imagine Github being critical infrastructure for you... The ineptitude...
Post reply on HN