‹ 返回事件歷史

Incident with Pull Requests, Git Operations and Issues

已復原較大故障GitHub
2026年11月4日星期三 17:49 至 2026年11月4日星期三 19:50(2 小時)
受影響元件
Git Operations
API Requests
Issues
Pull Requests
Actions
更新記錄
已復原2026年11月4日星期三 19:50

n November 4, 2026, between 09:35 UTC and 11:43 UTC, customers experienced intermittent errors and timeouts across GitHub.com, primarily on actions that write data. At peak, about 20% of pull request write operations (such as merging, commenting, and reviewing) failed, along with about 10% of issue creates and edits and 10–15% of project item edits. Git pushes over SSH, REST and GraphQL API requests, code scanning uploads, releases, and package operations were also affected, and about 1% of Actions runs were delayed by more than five minutes or failed to start. Overall, nearly 4% of all requests to GitHub.com failed at the worst point. Reads were largely unaffected, and retrying a failed action a short time later usually succeeded.<br /><br />The incident was triggered by a burst of concurrent updates to the same database record, which tied up all available connections to one of our primary databases. Although that contention cleared, the backlog of waiting requests kept our database connection layer overloaded, and it did not recover on its own. We mitigated the incident by failing over to a new primary database host. Most services recovered by 11:31 UTC, and Actions recovered by 11:43 UTC.<br /><br />Since the incident, we have disabled the code path that triggered the contention, increased the processing capacity of our database connection layer by 50%, and added alerting to detect this type of overload earlier. We are also improving our procedures so we can fail over sooner in similar situations.

監控中2026年11月4日星期三 19:43

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

排查中2026年11月4日星期三 19:30

The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

排查中2026年11月4日星期三 19:17

We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available.

排查中2026年11月4日星期三 19:11

API Requests is experiencing degraded performance. We are continuing to investigate.

排查中2026年11月4日星期三 18:38

We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation.

排查中2026年11月4日星期三 17:53

Pull Requests is experiencing degraded availability. We are continuing to investigate.

排查中2026年11月4日星期三 17:50

Actions is experiencing degraded performance. We are continuing to investigate.

排查中2026年11月4日星期三 17:49

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

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

關於這些資料

GitHub 的事件資料來自哪裡?

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

如何解讀元件狀態列?

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

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

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

持續時間如何計算?

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

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