Live / GitHub / Incident
GitHub: Incident with Webhooks API
GitHub · github.comMinor incidentResolved2026-11-12 19:33 UTC
Public — what happened
Summary
GitHub said it began investigating a problem with its Webhooks API at 18:43 UTC on 2026-11-12, which it rated as minor. About nine minutes later it reported that timeouts and errors were affecting roughly 1% of customer traffic, and that it was looking at ways to reduce the impact. By 19:20 UTC GitHub said traffic had recovered and the degradation was mitigated, and it kept watching for stability before marking the incident resolved at 19:33 UTC. The company did not state a cause in the updates provided.
Affected
Webhooks
Timeline
- Started — 2026-11-12 18:43 UTC
- Investigating — 2026-11-12 18:43 UTC (3 updates)
- Monitoring — 2026-11-12 19:20 UTC
- Resolved — 2026-11-12 19:33 UTC · 51 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.