‹ Back to incident history

Incident with Webhooks and Actions

ResolvedMajor outageGitHub
Monday, November 9, 2026 18:00 – Monday, November 9, 2026 19:50 (1 hr 50 min)
Affected components
Webhooks
Actions
Updates
ResolvedMonday, November 9, 2026 19:50

On November 9, 2026, from 09:23 to 11:40 UTC, one of our job queue clusters was degraded, delaying webhook deliveries, Actions workflow runs, and Dependabot and dependency graph updates. Until mitigation at 10:37 UTC, an average of 26% of webhook deliveries were delayed, peaking at 30%, and the backlog cleared by 11:40 UTC. Some deliveries were delayed by up to 3.5 hours, and delays for a small share began as early as 01:00 UTC. Actions skips events older than 30 minutes, so some workflow runs did not start. <br /><br />The incident was caused by a degraded host that had slowed one of the cluster's Kafka brokers since November 7. The broker stopped reporting the metrics our alerts rely on, so we did not identify it until it stalled the cluster on November 9. <br /><br />We mitigated the incident by removing the broker from service. We have since added an alert that pages us within 30 minutes when a host slows a broker this way, so we can remove the broker before it affects customers.

MonitoringMonday, November 9, 2026 19:45

The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.

InvestigatingMonday, November 9, 2026 19:42

Webhooks is experiencing degraded performance. We are continuing to investigate.

InvestigatingMonday, November 9, 2026 19:17

Webhooks is experiencing degraded availability. We are continuing to investigate.

InvestigatingMonday, November 9, 2026 19:06

The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

InvestigatingMonday, November 9, 2026 18:47

We've applied a mitigation and are monitoring for recovery.

InvestigatingMonday, November 9, 2026 18:28

We're investigating delays in Actions runs start times and webhook deliveries.

InvestigatingMonday, November 9, 2026 18:00

We are investigating reports of degraded performance for Actions and Webhooks

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview