‹ 返回事件歷史

Disruption with Dependabot Alerts

已復原輕微故障GitHub
2026年10月23日星期五 22:58 至 2026年10月24日星期六 02:51(3 小時 52 分鐘)
更新記錄
已復原2026年10月24日星期六 02:51

We identified that an advisory-publication driven fan-out was overwhelming Dependabot alert processing on repositories by saturating the queue with its own events, delaying processing of events related to repository pushes.<br /><br />We have now isolated this fan-out and applied a throttle so it runs at a fixed rate and cannot delay other events. This remediation has successfully prevented a new fan-out process impacting users.

監控中2026年10月24日星期六 02:36

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

排查中2026年10月24日星期六 01:27

Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability. <br /><br />We're continuing to investigate and work to restore normal processing.

排查中2026年10月24日星期六 00:43

We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring progress and will share another update as we learn more.

排查中2026年10月24日星期六 00:11

We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring the rollout and will share another update as we learn more.

排查中2026年10月23日星期五 23:39

We’re scaling alert processing capacity to reduce the backlog causing delays in some Dependabot alerts closing after affected repositories have been updated. We’re continuing to monitor and will share another update as more information becomes available.

排查中2026年10月23日星期五 23:00

We’re investigating delays in some Dependabot alerts closing after affected repositories have been updated to address a vulnerability. Alert processing is backed up. We’ll share more information as it becomes available.

排查中2026年10月23日星期五 22:58

We are investigating reports of impacted performance for some GitHub services.

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

關於這些資料

GitHub 的事件資料來自哪裡?

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

如何解讀元件狀態列?

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

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

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

持續時間如何計算?

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

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