Disruption with GitHub services
On October 30, 2026, between 14:20 and 14:29 UTC, customers experienced errors across multiple GitHub services. Affected services include Git operations, GraphQL and REST API, Pull Requests, and Issues. At peak, about 3.5% of API requests failed. <br /><br />The incident was caused by slow database requests that held connections open longer than expected, which used all available connections to one of our primary databases. Service recovered at 14:29 UTC once connections were released. <br /><br />Since the incident, we have fixed the code path that held connections open and increased the processing capacity of our database connection layer. We are also improving alerting for this type of overload.
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
A temporarily overloaded component triggered a burst of errors between 14:21 and 14:30 UTC across numerous services. Component health has returned to normal and we continue to monitor while investigating the root cause.<br />
Issues is operating normally.
Pages is experiencing degraded performance. We are continuing to investigate.
Issues is experiencing degraded performance. We are continuing to investigate.
We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation.
We are investigating reports of impacted performance for some GitHub services.
關於這些資料
GitHub 的事件資料來自哪裡?
資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。
如何解讀元件狀態列?
每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。
為什麼有些服務查不到歷史?
只收錄提供公開官方狀態頁的服務。
持續時間如何計算?
按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。
完整的服務清單與即時狀態見狀態總覽