Live / GitHub / Incident
GitHub: Incident with Git Operations and Pull Requests
GitHub · github.comCritical outageResolved2026-11-10 17:55 UTC
Public — what happened
Summary
GitHub said it began investigating at 16:10 UTC on 2026-11-10 after reports of degraded performance affecting Actions and Pull Requests. It later described slower response times for Git operations and pull requests, along with delayed Actions workflows that are triggered from pull requests. GitHub reported Actions back to normal at 17:28 UTC, while pull request processing was still seeing some delays and failures at 17:46 UTC. The incident was marked resolved at 17:55 UTC, and GitHub did not state a cause in the updates provided.
Affected
Pull Requests, Actions
Timeline
- Started — 2026-11-10 16:10 UTC
- Investigating — 2026-11-10 16:10 UTC (8 updates)
- Resolved — 2026-11-10 17:55 UTC · 1h 44m 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.