Actions Job Delays

Timeline

1. 14:47 UTC GitHub status page · Reported Actions Job Delays
2. 14:47 UTC GitHub status page · Investigating We are investigating reports of degraded performance for Actions
3. 14:54 UTC GitHub status page · 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.
4. 15:02 UTC GitHub status page · 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.
5. 15:10 UTC GitHub status page · Monitoring The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
6. 15:20 UTC GitHub status page · Investigating Actions is experiencing degraded performance. We are continuing to investigate.
7. 15:29 UTC GitHub status page · 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.
8. 16:10 UTC GitHub status page · 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.
9. 16:48 UTC GitHub status page · Investigating We are currently applying a mitigation and anticipate recovery within thirty minutes.
10. 17:50 UTC GitHub status page · 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.
11. 17:56 UTC GitHub status page · 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…