Experiencing connection issues across Actions, Codespaces, and possibly other services
This summary is created by Generative AI and may differ from the actual content.
Overview
Multiple GitHub services, including Actions, Codespaces, GitHub Enterprise Importer, GitHub Enterprise Cloud trials with Data Residency, and Copilot Metrics API, experienced degraded performance between 14:07 UTC and 23:15 UTC on October 29th, 2025. This was caused by a broad outage in one of GitHub's service providers. GitHub applied mitigations, such as advising US Codespaces users to choose European or Asian regions and mitigating impact to most larger runner jobs, though ARM64 runners were still impacted. Full recovery was achieved only after the service provider's incident was resolved. GitHub is working to reduce critical path dependencies on the service provider and gracefully degrade experiences where possible for future resilience.
Impact
Users of Codespaces experienced an average connection error rate of 90%, peaking at 100% across all regions. GitHub Actions larger hosted runners saw 0.5% of overall workflow runs and 9.8% of larger hosted runner jobs failing or not starting within 5 minutes, with ARM64, GPU, and private networking runners still impacted after general mitigation. The GitHub Enterprise Importer service was degraded, with some users experiencing migration failures during git push operations and most users experiencing delayed migration processing. Initiation of new trials for GitHub Enterprise Cloud with Data Residency was delayed. Approximately 100 Copilot Metrics API requests for downloadable links failed.
Trigger
A broad outage in one of GitHub's service providers.
Detection
GitHub became aware of the incident by investigating reports of degraded performance for Actions starting around 16:17 UTC, and subsequently for Codespaces and other services.
Resolution
GitHub applied several mitigations, including advising US Codespaces users to choose European or Asian regions and mitigating impact to most larger runner jobs, though ARM64 runners remained affected. Full resolution was achieved only after the underlying incident at the service provider was resolved. GitHub is also working on long-term solutions to reduce critical path dependencies and implement graceful degradation for future resilience.
Root Cause
A broad outage in one of GitHub's service providers.