Incident with Actions (opens in new tab)

I'm frustrated with GitHub's stability, too, but we should be clear that GitHub wasn't down. They're one of the more honest services when it comes to posting service degradations, unlike some other platforms where teams will resist updating the status page until it's an undeniable site-wide outage.

> We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US region affecting 10% of runs. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.

> We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs

Frustrating if you were impacted, but from the comments here you'd think the entire site was down again.

Instead of repeating everything again (every comment at time of writing is a rehashing of something from other threads); why not just read old threads?

We're not treading new ground anymore.

Here's a few of the better ones in the last 2 weeks;

https://news.ycombinator.com/item?id=48012022

https://news.ycombinator.com/item?id=48010301

https://news.ycombinator.com/item?id=47924775

https://news.ycombinator.com/item?id=47881672

https://news.ycombinator.com/item?id=47877644

GitHub's COO shared this under-reported X post last month [1] on their exponential growth. I'd love to see more proactive messaging on their growth rate / vision for agentic interactions.

> … 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 in 2025, and now 2.1B minutes so far this week.

[1] https://x.com/kdaigle/status/2040164759836778878

All the more reason to donate to Forgejo/Codeberg[1][2] or contribute the code to SourceHut[3].

[1] https://liberapay.com/forgejo

[2] https://donate.codeberg.org/

[3] https://sr.ht/~sircmpwn/sourcehut/

Down to 84.88% uptime: https://mrshu.github.io/github-statuses/

Can't even do three 8s properly.

Why don’t they just raise GitHub actions prices? Supply and demand, that would sort itself

I don't know how art sites are handling AI. The cost to create has gone done multiple orders of magnitude. People are pushing more content into online services than ever before, and the rate is only increasing.

Do Github publish post-mortems?

Incidents spiked recently and I wonder what's repeatedly causing the issue.

Mistakes (preventable or not) can happen, but repeated failures is a systematic issue.

I'm using GitHub for my business and so do millions more. Might be time to prioritize paying customers, historically popular open source repos and PRs created by known human actors. Agents can wait, humans have much less patience.

Honestly I kind of feel for them - their traffic must be spiking like no tomorrow. Though still annoying when the team takes down time because GitHub is down...has anyone transitioned to something else successfully?

I re-ask this: https://news.ycombinator.com/item?id=47979968

If everyone is vibecoding, and SaaS plays have no moats anymore, and everyone says they are mad at Github's reliability...why aren't there like 10 viable replacements already?

Why are you still using Github?

How is the company morale at github? I imagine it to be really very depressing working at github right now with all these downtime. I know github is being used by AI agents like there is no tomorrow but there have also been en-shittification attempts at github and I have seen some comments tell me that github can be more efficient.

So what are people who are at github doing right now? Like what do the priorities look like?

Once again a reminder for people to look at codeberg. An Uptime of 84.88% is just not acceptable Github. I don't think that Github can come out of this personally. This problem has gone for too long and has become too large for people to ignore.

We get it.

We should probably take a break on these. It's probably more newsworthy now when GitHub is "up".

This is 100% AI's fault. It is a mix of more commits coming in, most likely code quality degradation, and I would not be surprised if capex that could be used to help with load is going towards AI instead