Incident with Actions
Between 16:39 and 16:57 UTC on November 5, 2026, some customers experienced failures starting workflow runs in GitHub Actions and Checks, and some in-progress runs failed. At peak, about 3% of workflow runs failed to queue, and roughly 0.21% of in-progress runs failed.<br /><br />The cause was resource exhaustion in a database service that stores Actions Checks data. Bursts of highly concurrent, large read requests put the service under memory pressure, which caused it to stall and reject requests.<br /><br />We mitigated the incident by failing over the affected database host. To prevent a recurrence, we have increased memory capacity across the affected database fleet. We will also be limiting concurrency of large queries to prevent heavy read traffic from causing a broad failure of critical workflows.
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
We are investigating reports of degraded performance for Actions
關於這些資料
GitHub 的事件資料來自哪裡?
資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。
如何解讀元件狀態列?
每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。
為什麼有些服務查不到歷史?
只收錄提供公開官方狀態頁的服務。
持續時間如何計算?
按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。
完整的服務清單與即時狀態見狀態總覽