GitHub experiences 504 timeouts due to a surge in anonymous traffic
GitHub announced on its status page on November 9, 2026, that it was investigating timeout issues caused by a surge in anonymous traffic. Users who are not logged in may encounter errors when accessing the site, while logged-in users are generally unaffected.
GitHub said it is currently debugging the anonymous traffic spike. Some users who are not logged in may see site errors, and CI tasks and release downloads may return a 504 Gateway Timeout if requests are initiated anonymously.
Original source:
Title: Increased timeouts due to surge in anonymous users Publisher: GitHub Publication date: 2026-11-09 URL: https://www.githubstatus.com/incidents/c9px7cw2ghrs Source type: official status update Verification status: The status page content was read in this instance; verification date 2026-11-08 Supporting content: supports the statements about a surge in anonymous traffic, users who are not logged in possibly encountering errors, and CI and release downloads possibly encountering 504s
ABAB AI Insight
This incident is similar to similar failure patterns in June and August 2026. At that time, GitHub also limited the impact to unauthenticated traffic, while requests from logged-in users were basically normal. In past incidents, GitHub attributed the cause to abnormal or abuse-related traffic surges at specific endpoints, leading unauthenticated request queues to time out.
Peaks in anonymous traffic can also affect release asset downloads in GitHub Actions and unauthenticated access to public repositories by external CI pipelines. GitHub previously mitigated such issues by using the load-balancing layer and application layer to selectively block abnormal traffic patterns, and said it was improving automated detection and emergency traffic-blocking deployment paths.
ABAB News · Laws of cognition
The protection mechanisms for anonymous traffic on public platforms prioritize the user experience of authenticated users when traffic surges occur.
CI and automation tools that rely on unauthenticated access will also experience 504 timeouts when the platform rate-limits traffic.
Peaks in anonymous traffic can be identified as an edge load issue rather than a site-wide service outage.