‹ 返回事件歷史

Incident with Actions

已復原輕微故障GitHub
2026年10月22日星期四 22:18 至 2026年10月22日星期四 23:18(1 小時)
受影響元件
Actions
更新記錄
已復原2026年10月22日星期四 23:18

On October 22, 2026, from 13:05 to 15:20 UTC, our event streaming platform was degraded resulting in elevated job processing latency spikes of 19-35 seconds and elevated job processing times of 4m – this resulted in delayed Actions workflow and step results (up to 13m), notifications (20m) and repository push events (12m). Recovery for repositories began at 14:32, with Actions recovery beginning at 14:59. The issue reoccurred at 16:26 again impacting Actions runs, repo push events, and notifications. Recovery began at 17:16 and completed at 2:07. <br /><br />The incident was caused by a significant increase in load coupled with client connection storms during a deployment overloading our Kafka event streaming brokers. <br /><br />To prevent future recurrence, we have expanded the affected cluster, shifted traffic to less loaded clusters, and implemented tunable client reconnect backoff.

監控中2026年10月22日星期四 23:18

GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.

監控中2026年10月22日星期四 23:17

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

排查中2026年10月22日星期四 23:06

We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.

排查中2026年10月22日星期四 22:35

Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.

排查中2026年10月22日星期四 22:19

We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.

排查中2026年10月22日星期四 22:18

We are investigating reports of degraded performance for Actions

事件資料來自 GitHub 官方狀態頁:查看官方原文

關於這些資料

GitHub 的事件資料來自哪裡?

資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。

如何解讀元件狀態列?

每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。

為什麼有些服務查不到歷史?

只收錄提供公開官方狀態頁的服務。

持續時間如何計算?

按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。

完整的服務清單與即時狀態見狀態總覽