Ubicloud - Impact across multiple GitHub products including Actions, Pages, and Copilot products. – Incident details

Impact across multiple GitHub products including Actions, Pages, and Copilot products.

ResolvedMajor outage33 minutes

Affected

GitHub Actions Service

Major outage from 8:48 PM to 8:56 PM, Degraded performance from 8:48 PM to 8:56 PM, Major outage from 8:56 PM to 8:56 PM, Degraded performance from 8:56 PM to 8:56 PM, Major outage from 8:56 PM to 8:57 PM, Degraded performance from 8:56 PM to 8:57 PM, Major outage from 8:57 PM to 9:07 PM, Degraded performance from 8:57 PM to 9:07 PM, Operational from 9:07 PM to 9:21 PM

GitHub → Actions

Major outage from 8:48 PM to 9:07 PM, Operational from 9:07 PM to 9:21 PM

GitHub → Webhooks

Degraded performance from 8:48 PM to 9:07 PM, Operational from 9:07 PM to 9:21 PM

  • ResolvedUTC

    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.

  • UpdateUTC

    The backlog of Actions jobs has been fully processed. We’re observing full recovery across all impacted services.

  • UpdateUTC

    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.

  • MonitoringUTC

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

  • UpdateUTC

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

  • UpdateUTC

    We’re investigating issues impacting multiple GitHub products including Actions, Pages, and Copilot products.

  • UpdateUTC

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

  • UpdateUTC

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

  • UpdateUTC

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

  • InvestigatingUTC

    We are investigating reports of degraded availability for Pages