ChangeIntel IT change radar
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
Resolved GitHub · degraded service

Incident with Actions and Pages

Posted 4 Nov 16:05 UTC, last seen today 13:21 UTC.

GitHub status pageOn the status board
Unknown Duration: the provider stated no start
10Updates posted
4Other incidents at the same time

What it affected

As the provider names it

WebhooksActionsPages

What the provider posted

Newest first
  1. 4 Nov 17:01 UTCResolvedOn November 4, 2026, between 15:49 UTC and 16:48 UTC, and again between 17:20 UTC and 17:55 UTC, GitHub Actions, Pages, Webhooks, Code Scanning, and Copilot coding agent experienced delays. During this time, Actions workflow runs and job status updates were delayed by up to 25 minutes. Pages deployments dropped to about 4% of normal volume, webhook deliveries dropped to about 58% of normal volume, and Code Scanning analyses and Copilot coding agent sessions were delayed. Delayed events were processed after mitigation. This incident was caused by a configuration change to an internal event-routing service that unexpectedly paused delivery of several event streams. The change depended on feature flags that were not set up as intended, which the service did not handle gracefully. We mitigated the first period by rolling back the configuration change at 16:14 UTC. The code change itself was not reverted by the rollback, so a subsequent deployment reintroduced it. We mitigated the second period at 17:40 UTC by rolling back again, then processed queued events and cleared backlogs. We are taking several steps to prevent a repeat. The routing service will keep its existing behavior when a feature toggle is missing, so a misconfigured flag can no longer pause delivery. We are adding a pre-deploy check that each routing flag exists and is registered under the correct owning service, and we are making flag ownership less error-prone to set. We are also improving alerting so we detect paused event delivery sooner.
  2. 4 Nov 17:01 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. 4 Nov 16:49 UTCUpdateThe degradation has been mitigated. We are monitoring to ensure stability.
  4. 4 Nov 16:48 UTCMonitoringThe degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
  5. 4 Nov 16:45 UTCUpdateThe degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
  6. 4 Nov 16:34 UTCUpdateWe have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
  7. 4 Nov 16:17 UTCUpdateActions is experiencing degraded availability. We are continuing to investigate.
  8. 4 Nov 16:12 UTCUpdateWebhooks is experiencing degraded performance. We are continuing to investigate.
  9. 4 Nov 16:11 UTCUpdateWe are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.
  10. 4 Nov 16:05 UTCInvestigatingWe are investigating reports of degraded performance for Actions and Pages

Around it

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

Keep track

What changed

  1. Services: Actions, Pages → Webhooks, Actions, Pages
  2. Status: Monitoring → Resolved · Incident state: Ongoing → Ended
  3. Status: Investigating → Monitoring
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 (11)

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

  1. 8 Nov 2026 · 16:47:15 UTC ServicesActions, Pages → Webhooks, Actions, Pages
  2. 7 Nov 2026 · 01:08:43 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 4, 2026, between 15:49 UTC and 16:48 UTC, and again between 17:20 UTC and 17:55 UTC, GitHub Actions, Pages, Webhooks, Code Scanning, and Copilot coding agent experienced delays. During this time, Actions workflow runs and job status updates were delayed by up to 25 minutes. Pages deployments dropped to about 4% of normal volume, webhook deliveries dropped to about 58% of normal volume, and Code Scanning analyses and Copilot coding agent sessions were delayed. Delayed events were processed after mitigation. This incident was caused by a configuration change to an internal event-routing service that unexpectedly paused delivery of several event streams. The change depended on feature flags that were not set up as intended, which the service did not handle gracefully. We mitigated the first period by rolling back the configuration change at 16:14 UTC. The code change itself was not reverted by the rollback, so a subsequent deployment reintroduced it. We mitigated the second period at 17:40 UTC by rolling back again, then processed queued events and cleared backlogs. We are taking several steps to prevent a repeat. The routing service will keep its existing behavior when a feature toggle is missing, so a misconfigured flag can no longer pause delivery. We are adding a pre-deploy check that each routing flag exists and is registered under the correct owning service, and we are making flag ownership less error-prone to set. We are also improving alerting so we detect paused event delivery sooner.
  3. 4 Nov 2026 · 17:04:04 UTC StageMonitoring → Resolved
  4. 4 Nov 2026 · 17:04:04 UTC Observed stateOngoing → Ended
  5. 4 Nov 2026 · 17:04:04 UTC SummaryThe degradation has been mitigated. We are monitoring to ensure stability. → 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.
  6. 4 Nov 2026 · 16:53:54 UTC SummaryThe degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability. → The degradation has been mitigated. We are monitoring to ensure stability.
  7. 4 Nov 2026 · 16:48:50 UTC StageInvestigating → Monitoring
  8. 4 Nov 2026 · 16:48:50 UTC SummaryWe have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs. → The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
  9. 4 Nov 2026 · 16:38:42 UTC SummaryActions is experiencing degraded availability. We are continuing to investigate. → We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs.
  10. 4 Nov 2026 · 16:18:25 UTC SummaryWebhooks is experiencing degraded performance. We are continuing to investigate. → Actions is experiencing degraded availability. We are continuing to investigate.
  11. 4 Nov 2026 · 16:13:20 UTC SummaryWe are investigating reports of degraded performance for Actions and Pages → Webhooks is experiencing degraded performance. We are continuing to investigate.
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

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.