‹ Back to incident history

Incident with Actions and Pages

ResolvedMajor outageGitHub
Thursday, November 5, 2026 00:05 – Thursday, November 5, 2026 01:01 (55 min)
Affected components
Webhooks
Actions
Pages
Updates
ResolvedThursday, November 5, 2026 01:01

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. <br /><br />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. <br /><br />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.

MonitoringThursday, November 5, 2026 00:49

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

MonitoringThursday, November 5, 2026 00:48

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

InvestigatingThursday, November 5, 2026 00:45

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

InvestigatingThursday, November 5, 2026 00:34

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.

InvestigatingThursday, November 5, 2026 00:17

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

InvestigatingThursday, November 5, 2026 00:12

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

InvestigatingThursday, November 5, 2026 00:11

We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.

InvestigatingThursday, November 5, 2026 00:05

We are investigating reports of degraded performance for Actions and Pages

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