已歸檔的官方INCIDENT

Actions delays in starting runs

GitHub · 最近儲存的提供方狀態:resolved

當前服務報告 →

官方來源文字以原始語言顯示。

這是歷史證據。

最近儲存的事件狀態不是當前服務狀態。來源列表可能不完整,事件從來源消失不確認恢復。請開啟當前報告或官方來源檢視較新證據。

已儲存事件詳情

提供方狀態
resolved
提供方影響程度
minor
提供方記錄建立時間
24 Aug 2026, 13:56:54 UTC
提供方記錄更新時間
25 Aug 2026, 01:36:32 UTC
提供方明確報告的開始時間
24 Aug 2026, 13:56:54 UTC
提供方明確報告的結束時間
24 Aug 2026, 14:34:42 UTC

提供方報告的受影響元件

  • Actions br0l2tvcx85d

這些關聯描述此事件的報告範圍。不能確認當前元件可用性或已核實依賴關係。

記錄建立時間未必是故障開始時間。未報告的時間保持不可用。我們不根據收集時間計算故障時長。

已儲存修訂中的提供方更新

最新優先。最多顯示最近 20 份已儲存內容修訂中的 100 條不同更新。同一提供方時間的文字修訂單獨保留。

  1. resolved

    On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewhere. During this period, events assigned to the affected component accumulated until an automatic rebalance redirected processing to healthy components at 13:54 UTC. The queue backlog was cleared at 14:00 UTC, and processing returned to normal by 14:04 UTC. <br /><br />To prevent a recurrence, we are improving detection and automated remediation for unhealthy nodes that aren’t fully offline. We are also strengthening application-level resiliency, so stalled consumers are automatically removed quickly and their work reassigned without waiting for the affected node to recover.

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到
  2. monitoring

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

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到
  3. investigating

    Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到
  4. investigating

    We are investigating reports of degraded performance for Actions

    在 06 Oct 2026, 13:58:39 UTC 的已儲存修訂中觀察到