Live / GitHub / Incident
GitHub: Disruption with GitHub services
GitHub · github.comCritical outageResolved2026-10-30 15:02 UTC
Public — what happened
Summary
GitHub said it began investigating reports of reduced performance across several of its services at 14:31 UTC on October 30, 2026, and it later listed Issues and Pages as affected. The company said an overloaded component caused a short burst of errors across many services between 14:21 and 14:30 UTC, and that the component's health had returned to normal while it kept looking into the root cause. GitHub reported Issues back to normal by 14:45 UTC and Pages mitigated by 14:49 UTC, and it marked the incident resolved at 15:02 UTC.
Affected
Issues, Pages
Timeline
- Started — 2026-10-30 14:31 UTC
- Investigating — 2026-10-30 14:31 UTC (6 updates)
- Monitoring — 2026-10-30 14:49 UTC
- Resolved — 2026-10-30 15:02 UTC · 32 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 45, 2026, our weekly internet health report.