- Level
- confirmed
- Worst impact
- Degraded
- Components
- Actions
- Down Index
- 40of 100
What to do
Check whether you use GitHub Actions 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 3h 9m it lasted.
Anything that failed between 2026-10-01 14:47 UTC and 2026-10-01 17:56 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 10
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.
provider
- investigating
Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.
provider
- monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.
provider
- investigating
We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.
provider
- investigating
We are currently applying a mitigation and anticipate recovery within thirty minutes.
provider
- investigating
GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.
provider
- resolved
On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and 0.196% of jobs failed to start. A routing change at our cloud provider concentrated API traffic on a single backend, causing an increase in rate-limit errors. Incorrect retry behavior in the provider’s inventory service added load to the affected APIs, compounding the rate limiting. This disrupted runner provisioning and reduced available capacity in affected regions. The resulting increase in demand in unaffected regions exposed a concurrency limit in our job-assignment system, delaying jobs even where runners were available. During the response, we increased job-assignment concurrency, scaled runner capacity, and worked with our cloud provider to reduce API load by excluding our runner subscriptions from its inventory service. By approximately 16:15 UTC, jobs were starting and executing as expected. We continued mitigation and monitoring until the incident was resolved at 17:56 UTC. Our cloud provider has since increased resource-management API rate limits for our workloads. To reduce the likelihood and impact of similar incidents, we are also adding more granular rate-limiting alerts and updating our job-assignment system to handle increased demand across fewer available regions.
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-e1bc6a6a42
Is GitHub Actions still down?
No, this incident was resolved 2026-10-01 17:56 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
3h 9m, from 2026-10-01 14:47 UTC to 2026-10-01 17:56 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named Actions.
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.