[2026-10-01] Incident Thread #209278
Replies: 11 comments 4 replies
UpdateWe 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. |
UpdateRun-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. |
UpdateWe 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. |
UpdateWe 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. |
UpdateWe are currently applying a mitigation and anticipate recovery within thirty minutes. |
|
Recovery to me |
UpdateGitHub 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. |
Incident ResolvedThis incident has been resolved. |
Uh oh!
There was an error while loading. Please reload this page.
❗ An incident has been declared:
Actions Job Delays
Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.
All reactions