Live / GitHub / Incident
GitHub: Degraded performance for multiple GitHub services
GitHub · github.comMinor incidentResolved2026-11-06 00:20 UTC
Public — what happened
Summary
GitHub said it began looking into slower performance and errors across several of its services at 23:36 UTC on November 5, 2026. It listed Git operations, Issues, Actions, Pages and API access as affected, and said some users might see failed requests or slow responses. By 00:06 UTC on November 6, GitHub said it had applied a mitigation and was seeing recovery, and it kept watching to confirm things were stable. The incident was marked resolved at 00:20 UTC, and the company did not state a cause in the updates provided.
Affected
Issues, Actions, Pages
Timeline
- Started — 2026-11-05 23:36 UTC
- Investigating — 2026-11-05 23:36 UTC (3 updates)
- Monitoring — 2026-11-06 00:06 UTC (2 updates)
- Resolved — 2026-11-06 00:20 UTC · 45 min 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.