Live / GitHub / Incident
GitHub: Incident with Actions and Checks API
GitHub · github.comCritical outageResolved2026-11-09 18:59 UTC
Public — what happened
Summary
GitHub said it began looking into an incident at 18:12 UTC on 2026-11-09, which it rated critical, after reports that GitHub Actions was less available than normal. Over the next several minutes the company said the problems also reached Webhooks and Pages, and that it was seeing elevated errors affecting Actions and the Checks API. At 18:43 UTC GitHub said the degradation had been mitigated and that it was monitoring for stability, and the incident was marked resolved at 18:59 UTC. GitHub did not name a cause in the updates provided.
Affected
Webhooks, Actions, Pages
Timeline
- Started — 2026-11-09 18:12 UTC
- Investigating — 2026-11-09 18:12 UTC (5 updates)
- Monitoring — 2026-11-09 18:43 UTC
- Resolved — 2026-11-09 18:59 UTC · 47 min 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.