Live  /  GitHub  /  Incident

GitHub: Incident with Git Operations

GitHub · github.comMinor incidentResolved2026-11-03 22:41 UTC
Public — what happened

Summary

GitHub said it began looking into reports of slower-than-normal Git Operations at 20:57 UTC on 2026-11-03, and it rated the incident as minor. By 21:37 UTC the company said it had identified the issue and started rolling out a mitigation, which it said was in place by 22:05 UTC. At 22:37 UTC GitHub reported significant improvement, though it noted that a small set of customers might still see some slowness, and it moved to monitoring. The incident was marked resolved at 22:41 UTC.

Affected

Git Operations

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 46, 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.