GitHub Copilot incident

Incident with Actions and Pages

Major Resolved Upstream link ↗

Started

November 4, 2026 at 04:05 PM UTC

Duration

55 min

Resolved

November 4, 2026 at 05:01 PM UTC

Updates timeline

  1. Investigating

    We are investigating reports of degraded performance for Actions and Pages

  2. Investigating

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

  3. Investigating

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

  4. Investigating

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

  5. Investigating

    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.

  6. Investigating

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

  7. Monitoring

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

  8. Monitoring

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

  9. Resolved

    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.

Get an email the next time GitHub Copilot goes down

Outage alerts for GitHub Copilot, straight to your inbox. No account needed, unsubscribe in every email.

Watching more than one service? A free account covers 5 services + a daily digest — and Pro is currently free.

Live GitHub Copilot status

Current indicator + 24h latency

All incidents

Cross-service timeline

Subscribe via RSS

Atom feed for any reader