GitHub Actions Hit by Runner Assignment Delays
GitHub Actions Has Problems

GitHub is investigating degraded performance in Actions, with delays in assigning GitHub-hosted runners affecting workflow start times across multiple configurations. The incident, first reported on October 5, 2026, remains under investigation as teams work to mitigate the impact.
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations.
- aliasxneo
We all know that AI is compounding the problem, but I wonder how much of it is actually AI writing extremely overly-complex (and likely inefficient) CI pipelines for vibe coders who have absolutely no idea what CI is or why they would need it. I'm sure the AI makes all sorts of great arguments to the user about why they need it and the user, none the wiser, blindly accepts it all. Why wouldn't they? It costs them absolutely nothing on an OSS repo.
I know that frontier models (Astra, Fable, Opus 5.5) at some point always end up writing a test that unnecessarily elongates CI. I've seen everything from literal sleep calls in a test unit to arbitrarily deciding a test needs to download a 100MB file to prove something works. As a engineer, I catch these, but a vibe coder has no idea there's probably hundreds of these in their code making CI take 10-20 minutes. Hell, they probably don't even click the "Actions" tab.
What a mess.
- progbits
Interestingly all the separate enterprise cloud instances show the same thing:
https://us.githubstatus.com/posts/details/P7VGB7I
https://au.githubstatus.com/posts/details/PO54BK8
https://eu.githubstatus.com/posts/details/PRESCZY
https://jp.githubstatus.com/posts/details/P0N7ZG5
What's the point of (supposedly) separate and isolated data residency deployments if they all have single point of failure?
- flohofwoe
GH Actions problems are so frequent that they are really not newsworthy anymore. Most of the time they don't even show up on the status page because they seem to be completely random (e.g. manually cancelling and restarting may resolve the issue).
- bushido
I recently got annoyed with the amount I was paying on actions for a single repo. And decided to use a Mac mini that I had lying around to become the sole self-hosted runner for that repository instead.
It was ridiculously easy to set up, reduced my issues with GitHub significantly and the mini will literally pay for itself 3-4x over this year with the $$$ I'm saving not paying for GH actions.
The most surprising part for me was not the cost savings, but that all my workflow runtimes went down by about 70-80%.
- gherkinnn
It would result in a lot less noise if we got updates for when GitHub is up!