Impact across multiple GitHub products including Actions, Pages, and Copilot products.
On November 11, 2026, from 20:05 to 21:02 UTC, customers experienced delayed or failed Actions workflow starts, webhook errors and delivery delays, slower GitHub Apps API requests, and reduced availability of Copilot features, including Code Review. GitHub Pages builds were also delayed.<br /><br />Nearly all GitHub Actions runs triggered between 20:18 and 20:55 UTC were delayed or failed, leaving approximately 3.4 million partially created runs that are being canceled. No GitHub Pages deployments completed during the incident. In the Central US data residency stamp, between 20:06 and 20:50 UTC, about 63% of webhook API requests failed and 27% of deliveries were not recorded; those deliveries reached their destinations but remain unavailable to view or redeliver. Between approximately 20:20 and 21:00 UTC, Copilot code review on github.com completed 87% fewer reviews than normal and some other Copilot features were also unavailable.<br /><br />The disruption was caused by an Azure Cosmos DB regional outage affecting database accounts used by these services. Per Cosmos’s RCA, a configuration change to the Central US gateways exposed a latent race condition under a specific high-load traffic pattern, causing gateway crashes and health-probe failures. Cosmos mitigated by rolling back the change. Service health recovered around 21:02 UTC, and the queued Actions backlog finished processing by 21:21 UTC.<br /><br />Our follow-up work focuses on validating regional database failover across affected services and developing tested recovery procedures. We are also improving recovery tools to quickly clear stuck Actions checks and runs after incidents so they do not remain uncancelable or block pull request merges.
The backlog of Actions jobs has been fully processed. We’re observing full recovery across all impacted services.
We’re seeing recovery across all services and continuing to monitor. The backlog of Actions jobs are being processed. We’ll update when we see full recovery.
The degradation affecting Actions, Copilot, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
Copilot is experiencing degraded availability. We are continuing to investigate.
We’re investigating issues impacting multiple GitHub products including Actions, Pages, and Copilot products.
Pages is experiencing degraded availability. We are continuing to investigate.
Webhooks is experiencing degraded performance. We are continuing to investigate.
Actions is experiencing degraded availability. We are continuing to investigate.
We are investigating reports of degraded availability for Pages
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