Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Incident with Webhooks and Actions

Posted 9 Nov 10:00 UTC, last seen today 13:21 UTC.

Unknown Duration: the provider stated no start
9Updates posted
6Other incidents at the same time

What it affected

As the provider names it

WebhooksActions

What the provider posted

Newest first
  1. 9 Nov 11:50 UTCResolvedOn 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. 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. 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.
  2. 9 Nov 11:50 UTCResolvedThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
  3. 9 Nov 11:45 UTCMonitoringThe degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
  4. 9 Nov 11:42 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
  5. 9 Nov 11:17 UTCUpdateWebhooks is experiencing degraded availability. We are continuing to investigate.
  6. 9 Nov 11:06 UTCUpdateThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
  7. 9 Nov 10:47 UTCUpdateWe've applied a mitigation and are monitoring for recovery.
  8. 9 Nov 10:28 UTCUpdateWe're investigating delays in Actions runs start times and webhook deliveries.
  9. 9 Nov 10:00 UTCInvestigatingWe are investigating reports of degraded performance for Actions and Webhooks

Around it

From the sources ChangeIntel reads; a match in time is not a cause

Keep track

What changed

  1. Status: Investigating → Resolved · Incident state: Ongoing → Ended
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (9)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 12 Nov 2026 · 19:17:42 UTC SummaryThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. → 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. 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. 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.
  2. 9 Nov 2026 · 11:51:46 UTC StageInvestigating → Resolved
  3. 9 Nov 2026 · 11:51:46 UTC Observed stateOngoing → Ended
  4. 9 Nov 2026 · 11:51:46 UTC SummaryWebhooks is experiencing degraded performance. We are continuing to investigate. → This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
  5. 9 Nov 2026 · 11:46:42 UTC SummaryWebhooks is experiencing degraded availability. We are continuing to investigate. → Webhooks is experiencing degraded performance. We are continuing to investigate.
  6. 9 Nov 2026 · 11:20:59 UTC SummaryThe degradation affecting Actions has been mitigated. We are monitoring to ensure stability. → Webhooks is experiencing degraded availability. We are continuing to investigate.
  7. 9 Nov 2026 · 11:15:53 UTC SummaryWe've applied a mitigation and are monitoring for recovery. → The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
  8. 9 Nov 2026 · 10:50:26 UTC SummaryWe're investigating delays in Actions runs start times and webhook deliveries. → We've applied a mitigation and are monitoring for recovery.
  9. 9 Nov 2026 · 10:30:08 UTC SummaryWe are investigating reports of degraded performance for Actions and Webhooks → We're investigating delays in Actions runs start times and webhook deliveries.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 13 Nov 13:11 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current