GitHub: Impact across multiple GitHub products including Actions, Pages, and Copilot products.
Affected components: ActionsCopilotPagesWebhooks
Discussed on Hacker News
- 81 points · 61 comments · posted · posted 6 min after the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Timeline of updates
- investigating
We are investigating reports of degraded availability for Pages
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
- investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
- investigating
Pages is experiencing degraded availability. We are continuing to investigate.
- investigating
We’re investigating issues impacting multiple GitHub products including Actions, Pages, and Copilot products.
- investigating
Copilot is experiencing degraded availability. We are continuing to investigate.
- monitoring
The degradation affecting Actions, Copilot, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
- monitoring
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.
- monitoring
The backlog of Actions jobs has been fully processed. We’re observing full recovery across all impacted services.
- resolvedEdited
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.
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.
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.
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.
Changes Rewindex caught on this incident
- Critical incident: Incident with Webhooks
- Incident updated: Impact across multiple GitHub products including Actions, Pages, and Copilot products.
- Incident updated: Impact across multiple GitHub products including Actions, Pages, and Copilot products.
- Incident updated: Impact across multiple GitHub products including Actions, Pages, and Copilot products.
- Incident silently edited: Impact across multiple GitHub products including Actions, Pages, and Copilot products.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-11 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fac7b8be7789c336…Version 2 captured
In the 2026-11-11 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d4f4e24f5303e0a1…Version 3 captured
In the 2026-11-11 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
749cb2d64b0ef709…Version 4 captured
In the 2026-11-11 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
1a4ec8ab6e87f3f9…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: critical) posted by GitHub, started 2026-11-11 20:48 UTC, resolved after 33 min, 10 update(s); edited after publishing.
- Title
- Impact across multiple GitHub products including Actions, Pages, and Copilot products.
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/company/github/incidents/dvy0t3mvh1lg
GitHub profileRecent GitHub incidentsAll outages on November 11, 2026GitHub in November 2026MarkdownJSON