← Back to GitHub History
minor✓ Resolved
Increased timeouts due to surge in anonymous users
Status
resolved
Duration
3h 11m
Updates
10
Coverage
0 articles
INCIDENT TIMELINE
✓ Resolved
This incident has been resolved.
resolved
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.
monitoring
We are resolving this incident as error rates have remained low and we have prepared additional protections.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
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.
investigating
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.
investigating
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.
monitoring
The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
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.
investigating
We are investigating reports of impacted performance for some GitHub services.
📊 TECHNICAL DETAILS
Internal ID
0e3acbdd-34bd-4e8e-be30-15a11f529f8d
External ID
c9px7cw2ghrs
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
3h 11m
Total Duration
10
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed