Incident with Dependabot
On October 30, 2026, between 20:15 and 21:56 UTC, an advisory-publication-driven fan-out caused an unexpected saturation of network connections to the Dependabot alerts datastore. During this period we observed a high rate of write failures on this datastore; users saw elevated failure rates when dismissing or resolving Dependabot alerts, as well as failures when linking Dependabot update pull requests to Dependabot security alerts. We also observed delays in creating and updating security alerts that extended through November 2, 2026.<br /><br />The unexpected fan-out was caused by a missing job queue throttle after the queues for the fan-out work were migrated as part of system maintenance. We have restored the fan-out throttle and further isolated and throttled these processes to guard against further disruptions.
The degradation has been mitigated. We are monitoring to ensure stability.
We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
We are investigating elevated errors when viewing some Dependabot alerts.
We are investigating reports of impacted performance for some GitHub services.
關於這些資料
GitHub 的事件資料來自哪裡?
資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。
如何解讀元件狀態列?
每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。
為什麼有些服務查不到歷史?
只收錄提供公開官方狀態頁的服務。
持續時間如何計算?
按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。
完整的服務清單與即時狀態見狀態總覽