GitHub Status

Resolved: On October 29th, 2025 between 14:07 UTC and 23:15 UTC, multiple GitHub services were degraded due to a broad outage in one of our service providers:

- Users of Codespaces experienced failures connecting to new and existing Codespaces through VSCode Desktop or Web. On average the Codespace connection error rate was 90% and peaked at 100% across all regions throughout the incident period.
- GitHub Actions larger hosted runners experienced degraded performance, with 0.5% of overall workflow runs and 9.8% of larger hosted runner jobs failing or not starting within 5 minutes. These recovered by 20:40 UTC.
- 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 were also delayed during this time.
- Copilot Metrics via the API could not access the downloadable link during this time. There were approximately 100 requests during the incident that would have failed the download. Recovery began around 20:25 UTC.

We were able to apply a number of mitigations to reduce impact over the course of the incident, but we did not achieve 100% recovery until our service provider’s incident was resolved.

We are working to reduce critical path dependencies on the service provider and gracefully degrade experiences where possible so that we are more resilient to future dependency outages.

Investigating: Codespaces is operating normally.

Investigating: Codespaces continues to recover

Investigating: Actions is operating normally.

Investigating: Actions has fully recovered.

Codespaces continues to recover. Regions across Europe and Asia are healthy, so US users may want to choose one of those regions following these instructions: https://docs.github.com/en/codespaces/setting-your-user-preferences/setting-your-default-region-for-github-codespaces.

We expect full recovery across the board before long.

Investigating: Codespaces is experiencing degraded performance. We are continuing to investigate.

Investigating: We are beginning to see small signs of recovery, but connections are still inconsistent across services and regions. We expect to see gradual recovery from here.

Investigating: We continue to see improvement in Actions larger runners jobs. Larger runners customers may still experience longer than normal queue times, but we expect this to rapidly improve across most runners.

ARM64 runners, GPU runners, and some runners with private networking may still be impacted.

Usage of Codespaces via VS Code (but not via SSH) is still degraded.

GitHub and Azure teams continue to collaborate towards full resolution.

Investigating: Codespaces is experiencing degraded availability. We are continuing to investigate.

Investigating: Codespaces is experiencing degraded performance. We are continuing to investigate.

Investigating: Impact to most larger runner jobs should now be mitigated. ARM64 runners are still impacted. GitHub and Azure teams continue to collaborate towards full resolution.

Investigating: Codespaces is experiencing degraded availability. We are continuing to investigate.

Investigating: Additional impact from this incident:

We’re currently investigating an issue causing the Copilot Metrics API report URLs to fail for 28-day and 1-day enterprise and user reports. We are collaborating with Azure teams to restore access as soon as possible.

Investigating: We are seeing ongoing connection failures across Codespaces and Actions, including Enterprise Migrations.

Linux ARM64 standard hosted runners are failing to start, but Ubuntu latest and Windows latest are not affected at this time.

SSH connections to Codespaces may be successful, but connections via VS Code are consistently failing.

GitHub and Azure teams are coordinating to mitigate impact and resolve the root issues.

Investigating: Actions impact is primarily limited to larger runner jobs at this time. This also impacts enterprise migrations.

Investigating: Codespaces is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded performance for Actions

Resolved: This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Investigating: Actions is operating normally.

Investigating: We have mitigated the issue for manually dispatching workflows via the UI

Investigating: We have identified the cause of the issue and are working towards a mitigation

Investigating: We are investigating issues manually dispatching workflows via the GitHub UI for Actions. The Workflow Dispatch API is unaffected.

Investigating: We are investigating reports of degraded performance for Actions

Resolved: On October 29th, 2025 between 14:07 UTC and 23:15 UTC, multiple GitHub services were degraded due to a broad outage in one of our service providers:

- Users of Codespaces experienced failures connecting to new and existing Codespaces through VSCode Desktop or Web. On average the Codespace connection error rate was 90% and peaked at 100% across all regions throughout the incident period.
- GitHub Actions larger hosted runners experienced degraded performance, with 0.5% of overall workflow runs and 9.8% of larger hosted runner jobs failing or not starting within 5 minutes. These recovered by 20:40 UTC.
- 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 were also delayed during this time.
- Copilot Metrics via the API could not access the downloadable link during this time. There were approximately 100 requests during the incident that would have failed the download. Recovery began around 20:25 UTC.

We were able to apply a number of mitigations to reduce impact over the course of the incident, but we did not achieve 100% recovery until our service provider’s incident was resolved.

We are working to reduce critical path dependencies on the service provider and gracefully degrade experiences where possible so that we are more resilient to future dependency outages.

Investigating: Codespaces is operating normally.

Investigating: Codespaces continues to recover

Investigating: Actions is operating normally.

Investigating: Actions has fully recovered.

Codespaces continues to recover. Regions across Europe and Asia are healthy, so US users may want to choose one of those regions following these instructions: https://docs.github.com/en/codespaces/setting-your-user-preferences/setting-your-default-region-for-github-codespaces.

We expect full recovery across the board before long.

Investigating: Codespaces is experiencing degraded performance. We are continuing to investigate.

Investigating: We are beginning to see small signs of recovery, but connections are still inconsistent across services and regions. We expect to see gradual recovery from here.

Investigating: We continue to see improvement in Actions larger runners jobs. Larger runners customers may still experience longer than normal queue times, but we expect this to rapidly improve across most runners.

ARM64 runners, GPU runners, and some runners with private networking may still be impacted.

Usage of Codespaces via VS Code (but not via SSH) is still degraded.

GitHub and Azure teams continue to collaborate towards full resolution.

Investigating: Codespaces is experiencing degraded availability. We are continuing to investigate.

Investigating: Codespaces is experiencing degraded performance. We are continuing to investigate.

Investigating: Impact to most larger runner jobs should now be mitigated. ARM64 runners are still impacted. GitHub and Azure teams continue to collaborate towards full resolution.

Investigating: Codespaces is experiencing degraded availability. We are continuing to investigate.

Investigating: Additional impact from this incident:

We’re currently investigating an issue causing the Copilot Metrics API report URLs to fail for 28-day and 1-day enterprise and user reports. We are collaborating with Azure teams to restore access as soon as possible.

Investigating: We are seeing ongoing connection failures across Codespaces and Actions, including Enterprise Migrations.

Linux ARM64 standard hosted runners are failing to start, but Ubuntu latest and Windows latest are not affected at this time.

SSH connections to Codespaces may be successful, but connections via VS Code are consistently failing.

GitHub and Azure teams are coordinating to mitigate impact and resolve the root issues.

Investigating: Actions impact is primarily limited to larger runner jobs at this time. This also impacts enterprise migrations.

Investigating: Codespaces is experiencing degraded performance. We are continuing to investigate.

Investigating: We are investigating reports of degraded performance for Actions