- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on GitHub Actions. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 55m it lasted.
Anything that failed between 2026-09-14 18:40 UTC and 2026-09-14 19:35 UTC may need a replay.Subscribe to GitHub Actions's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-actions works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub Actions 3
- investigating
We are investigating reports of impacted performance for some GitHub services.
provider
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
provider
- resolved
On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, 5.7% of larger-runner jobs were affected. A routine expansion of our compute capacity exposed a bug in how our provisioning system handled capacity records when selecting where to create runner virtual machines. This slowed the creation of new runners, leaving insufficient runner capacity to start affected jobs promptly. We restored normal provisioning by correcting the affected capacity records. We have fixed the underlying capacity-selection bug to prevent this failure from recurring. We have also added alerts for VM-record creation failures associated with this capacity issue.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2253991858
Is GitHub Actions still down?
No, this incident was resolved 2026-09-14 19:35 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
55m, from 2026-09-14 18:40 UTC to 2026-09-14 19:35 UTC, by the times GitHub Actions posted.
What caused it?
GitHub Actions hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub Actions's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.