Incident with API, Git, and Copilot requests
On November 3, 2026, between 12:34 and 13:51 UTC, some users experienced authentication failures and errors with the REST and GraphQL APIs, pull requests, Issues, and GitHub Copilot. On average, the error rate was 0.46% and peaked at 0.98% of API requests. Copilot API errors averaged 2.0% and peaked at 3.1%.<br /><br />This was caused by a bug in our process for replacing control-plane servers in one of our compute clusters. When a replacement server did not receive a timely response from the existing cluster, it incorrectly created a separate cluster. This stopped traffic from reaching much of the cluster's capacity and overloaded the authentication servers that were still handling requests.<br /><br />We mitigated the incident by removing the incorrectly configured server.<br />We are also fixing the replacement logic and adding safeguards to prevent servers in this state from serving traffic.
The degradation has been mitigated. We are monitoring to ensure stability.
API Requests is operating normally.
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Issues is experiencing degraded performance. We are continuing to investigate.
We are investigating reports of degraded performance for Copilot
關於這些資料
GitHub 的事件資料來自哪裡?
資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。
如何解讀元件狀態列?
每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。
為什麼有些服務查不到歷史?
只收錄提供公開官方狀態頁的服務。
持續時間如何計算?
按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。
完整的服務清單與即時狀態見狀態總覽