Live / GitHub / Incident
GitHub: Increase in timeouts for some unauthenticated users
GitHub · github.comMinor incidentResolved2026-11-08 12:32 UTC
Public — what happened
Summary
GitHub said it began looking into reports of slower performance for some of its services at 10:36 UTC on 2026-11-08, and later described the problem as mainly affecting users who were not signed in, including API requests. At 11:50 UTC the company said it had found a faulty component and was redeploying it. By 11:56 UTC GitHub said the API slowdown had been reduced and it was watching for stability, and the incident was marked resolved at 12:32 UTC. GitHub rated the incident as minor.
Affected
API Requests
Timeline
- Started — 2026-11-08 10:36 UTC
- Investigating — 2026-11-08 10:36 UTC (5 updates)
- Resolved — 2026-11-08 12:32 UTC · 1h 57m 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 46, 2026, our weekly internet health report.