‹ 返回事件歷史

Incident with Actions, Pull Requests and Issues

已復原輕微故障GitHub
2026年10月12日星期一 20:21 至 2026年10月13日星期二 04:16(7 小時 54 分鐘)
受影響元件
Issues
Pull Requests
Actions
更新記錄
已復原2026年10月13日星期二 04:16

On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. <br /><br />The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC. <br /><br />The incident was triggered through a latent condition in our notifications delivery pipeline that put a high volume of an expensive query on our sharded database replicas. This reduced available database capacity to serve requests for Issues, Pull Requests, Projects, and Actions.<br /><br />We have fixed the notifications pipeline’s code path that issued the expensive query. We are also improving resilience of the database layer to reduce the likelihood and impact of similar incidents.

排查中2026年10月13日星期二 03:28

Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.

排查中2026年10月13日星期二 01:34

Web and email notifications continue to be delayed as we work through a backlog of notifications.

排查中2026年10月12日星期一 23:50

Notifications have resumed but will continue to be delayed as we work through a backlog.

排查中2026年10月12日星期一 23:19

We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.

排查中2026年10月12日星期一 22:37

We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.

排查中2026年10月12日星期一 22:36

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

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

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

排查中2026年10月12日星期一 21:38

Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.

排查中2026年10月12日星期一 21:02

Pull Requests is operating normally.

排查中2026年10月12日星期一 20:57

We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.

排查中2026年10月12日星期一 20:33

Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.

排查中2026年10月12日星期一 20:21

We are investigating reports of degraded performance for Actions, Issues and Pull Requests

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

關於這些資料

GitHub 的事件資料來自哪裡?

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

如何解讀元件狀態列?

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

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

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

持續時間如何計算?

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

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