GitHub reported this minor-impact incident on its official status page on Oct 1, 2026, 14:47 UTC. It was resolved after 3h 9m.
Right now GitHub is operational. Live GitHub status →
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
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.
We are currently applying a mitigation and anticipate recovery within thirty minutes.
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.
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.
Actions is experiencing degraded performance. We are continuing to investigate.
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
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.
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.
We are investigating reports of degraded performance for Actions
Overlapping incidents aren't necessarily related.
GitHub reported 49 incidents in the last 90 days, 15 of them major or critical. A typical incident lasted 1h 16m. See GitHub's uptime and incident history