Live  /  GitHub  /  Incident

GitHub: Incident with Webhooks and Actions

GitHub · github.comMajor incidentResolved2026-11-09 11:50 UTC
Public — what happened

Summary

GitHub reported a major incident that began at 10:00 UTC on 2026-11-09, affecting Actions and Webhooks. The company said Actions runs were slow to start and webhook deliveries were delayed. GitHub said it applied a mitigation by 10:47 UTC and that Actions was back to normal by 11:06 UTC, but Webhooks then showed reduced availability and performance around 11:17 and 11:42 UTC. GitHub said the Webhooks problem was mitigated at 11:45 UTC, and the incident was marked resolved at 11:50 UTC. No cause was given in the updates.

Affected

Webhooks, Actions

As listed on GitHub’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the GitHub status & history page.

Related: GitHub status & history. SquidGrid is not affiliated with GitHub.