Live / GitHub / Incident
GitHub: Incident with Pull Requests, Git Operations and Issues
GitHub · github.comMajor incidentResolved2026-11-04 11:50 UTC
Public — what happened
Summary
GitHub said it began investigating at 09:49 UTC on 2026-11-04 after reports of degraded performance affecting Git Operations, Issues and Pull Requests. It later said Actions and API Requests were also affected, and described elevated errors and intermittent failures in which some requests might fail or be delayed. GitHub did not name a cause in its updates. It reported the problems for API Requests, Git Operations, Issues and Pull Requests as mitigated at 11:30 UTC and for Actions at 11:43 UTC, and the incident was marked resolved at 11:50 UTC.
Affected
Git Operations, API Requests, Issues, Pull Requests, Actions
Timeline
- Started — 2026-11-04 09:49 UTC
- Investigating — 2026-11-04 09:49 UTC (7 updates)
- Monitoring — 2026-11-04 11:43 UTC
- Resolved — 2026-11-04 11:50 UTC · 2h 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.