Live / GitHub / Incident
GitHub: Incident with Pull Requests
GitHub · github.comMajor incidentResolved2026-11-13 18:29 UTC
Public — what happened
Summary
GitHub said that on November 13, 2026, starting at 15:47 UTC, Pull Requests had reduced availability, with some attempts to merge timing out. The company reported that the problem first touched about 3% of requests, and after it took steps to reduce the impact, that share fell to under 1%. GitHub said the degradation was mitigated by 17:28 UTC and that it kept monitoring stability, and the incident was marked resolved at 18:29 UTC. The company did not name a cause in the text provided.
Affected
Pull Requests
Timeline
- Started — 2026-11-13 15:47 UTC
- Investigating — 2026-11-13 15:47 UTC (5 updates)
- Monitoring — 2026-11-13 17:28 UTC (2 updates)
- Resolved — 2026-11-13 18:29 UTC · 2h 42m 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 47, 2026, our weekly internet health report.