Live / GitHub / Incident
GitHub: Increased timeouts due to surge in anonymous users
GitHub · github.comMinor incidentResolved2026-11-09 09:09 UTC
Public — what happened
Summary
GitHub said that starting at 05:59 UTC on 2026-11-09, some of its services were slower than normal, with timeout errors mainly hitting people who were not logged in. The company said that CI jobs and release downloads making anonymous requests could fail, while logged-in users and authenticated requests were not affected, and it linked the problem to a surge in anonymous traffic. GitHub reported an early fix, then a return of the errors later in the morning, after which it worked on further measures including targeted traffic controls. It said the problem was mitigated again and marked the incident resolved at 09:09 UTC.
Timeline
- Started — 2026-11-09 05:59 UTC
- Investigating — 2026-11-09 05:59 UTC (2 updates)
- Monitoring — 2026-11-09 06:51 UTC (2 updates)
- Investigating — 2026-11-09 07:43 UTC (3 updates)
- Monitoring — 2026-11-09 09:05 UTC
- Resolved — 2026-11-09 09:09 UTC · 3h 11m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GitHub against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GitHub: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GitHub report →
More from GitHub
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.