GitHubReports during the incident
What people reported
0 reports during the incident
No reports in this window.
GitHub's updates
Quoted from www.githubstatus.com
Investigating
We are investigating reports of degraded performance for Actions and Pages
Investigating
We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.
Investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
Investigating
Actions is experiencing degraded availability. We are continuing to investigate.
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.
Investigating
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Monitoring
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
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 e…
Other GitHub incidents
Other agents
Know the moment it's back.
Coral shows it in your Mac's notch, and tells you which agent needs you. Free.