Increased timeouts due to surge in anonymous users
On November 9, 2026, GitHub.com experienced intermittent timeouts between approximately 05:10 and 08:15 UTC. Across that full window, 6.5% of recorded requests to github.com timed out, with a five-minute peak of 13.9% between 07:40 and 07:45 UTC. Release downloads were more affected: 38.5% of recorded requests timed out, peaking at 76% during that same five-minute interval. The two main error waves lasted about two hours and ten minutes in total, with recovery between them. The errors affected repository browsing and disrupted some CI workflows and Copilot code review jobs. Contrary to our earlier updates, follow-up analysis confirmed at least 6,236 authenticated requests that timed out, affecting activity feeds, access to uploaded attachments and repository archive downloads. Errors occurred during elevated traffic to our web infrastructure that handles unauthenticated requests. Impact was mitigated when traffic causing pressure on this system was alleviated. Our follow-up work focuses on improving capacity monitoring, traffic prioritization improvements, and automated protection against traffic spikes.
We are resolving this incident as error rates have remained low and we have prepared additional protections.
The degradation has been mitigated. We are monitoring to ensure stability.
Error rates have declined again, and we’re preparing targeted traffic controls while monitoring for a recurrence. Logged-in users and authenticated requests have not been affected.
We are continuing to observe high rates of 504 errors for anonymous requests. We are continuing to work on mitigation. Logged-in users and authenticated requests are unaffected.
We have observed a repeated increase in 504 errors for anonymous and unauthenticated traffic, including users who are not logged in and release downloads. We are continuing to investigate and apply mitigations.
The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.
The degradation has been mitigated. We are monitoring to ensure stability.
We are debugging a spike in anonymous traffic. Some users who are not logged in may see errors on the site. CI jobs and release downloads may fail with a 504 Gateway Timeout status if they make anonymous calls.
We are investigating reports of impacted performance for some GitHub services.
關於這些資料
GitHub 的事件資料來自哪裡?
資料來自GitHub 官方狀態頁,每 5 分鐘同步,保留最近 90 天。詳情頁提供官方記錄連結。
如何解讀元件狀態列?
每格代表一天。綠色表示無異常記錄,黃色表示部分降級,紅色表示較大故障,灰色表示無資料。可用率統計涵蓋最近 90 天。
為什麼有些服務查不到歷史?
只收錄提供公開官方狀態頁的服務。
持續時間如何計算?
按官方標記的開始至復原時間計算。進行中的事件計算至目前時間。跨天事件會顯示在每個受影響的日期。
完整的服務清單與即時狀態見狀態總覽