GitHub experienced a minor incident on October 1, 2026 affecting Actions, lasting 3h 9m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 01, 2026, 02:47 PM UTC
We are investigating reports of degraded performance for Actions
- investigating Oct 01, 2026, 02:54 PM UTC
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.
- investigating Oct 01, 2026, 03:02 PM UTC
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.
- monitoring Oct 01, 2026, 03:10 PM UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- investigating Oct 01, 2026, 03:20 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating Oct 01, 2026, 03:29 PM UTC
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.
- investigating Oct 01, 2026, 04:10 PM UTC
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.
- investigating Oct 01, 2026, 04:48 PM UTC
We are currently applying a mitigation and anticipate recovery within thirty minutes.
- investigating Oct 01, 2026, 05:50 PM UTC
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.
- resolved Oct 01, 2026, 05:56 PM UTC
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.