已归档的官方INCIDENT

Actions Job Delays

GitHub · 最近保存的提供方状态:resolved

当前服务报告 →

官方来源文字以原始语言显示。

这是历史证据。

最近保存的事件状态不是当前服务状态。来源列表可能不完整,事件从来源消失不确认恢复。请打开当前报告或官方来源查看较新证据。

已保存事件详情

提供方状态
resolved
提供方影响程度
minor
提供方记录创建时间
01 Oct 2026, 14:47:48 UTC
提供方记录更新时间
09 Oct 2026, 21:52:10 UTC
提供方明确报告的开始时间
01 Oct 2026, 14:47:48 UTC
提供方明确报告的结束时间
01 Oct 2026, 17:56:54 UTC

提供方报告的受影响组件

  • Actions br0l2tvcx85d

这些关联描述此事件的报告范围。不能确认当前组件可用性或已核实依赖关系。

记录创建时间未必是故障开始时间。未报告的时间保持不可用。我们不根据采集时间计算故障时长。

已保存修订中的提供方更新

最新优先。最多显示最近 20 份已保存内容修订中的 100 条不同更新。同一提供方时间的文字修订单独保留。

  1. 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. <br /><br />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. <br /><br />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. <br /><br />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.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  2. resolved

    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.

    在 06 Oct 2026, 13:58:39 UTC 的已保存修订中观察到
  3. 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.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  4. investigating

    We are currently applying a mitigation and anticipate recovery within thirty minutes.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  5. 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.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  6. 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.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  7. investigating

    Actions is experiencing degraded performance. We are continuing to investigate.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  8. monitoring

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  9. 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.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  10. 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.

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到
  11. investigating

    We are investigating reports of degraded performance for Actions

    在 09 Oct 2026, 21:52:35 UTC 的已保存修订中观察到