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

As listed on GitHub’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the GitHub status & history page.

Related: GitHub status & history. SquidGrid is not affiliated with GitHub.