Is GitHub Codespaces down?

We are investigating reports of degraded performance for Issues and Webhooks

We are investigating Increased latency and timeouts across multiple GitHub services.

Git Operations is experiencing degraded performance. We are continuing to investigate.

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

Pull Requests is experiencing degraded availability. We are continuing to investigate.

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

Pull Requests is experiencing degraded performance. We are continuing to investigate.

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

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

Git Operations is operating normally.

Actions and Packages are operating normally.

Latency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.

Pages is operating normally.

Pull Requests is operating normally.

The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.

Webhooks is operating normally.

The degradation has been mitigated. We are monitoring to ensure stability.

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.

We are investigating reports of degraded performance for Actions

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

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

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

Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.

A mitigation was applied and services have recovered.  Actions is working through queued work before fully recovering.

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

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.

We are investigating reports of degraded performance for Codespaces

We are experiencing degraded performance in Codespaces related to creating a new Codespace or starting an existing Codespace from the VS Code editor. SSH connections to Codespaces are not impacted. We are working toward mitigation and will continue to keep you updated on progress.

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

We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.

Our provider is implementing a mitigation and we are seeing signs of recovery.

The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.

On April 16, 2026 between 09:30 UTC and 17:15 UTC, users experienced failures when attempting to connect to GitHub Codespaces via the VS Code editor. During this time, approximately 40% of codespace start operations failed. Users connecting via SSH were not impacted. The issue was caused by a failure in an upstream download service that prevented the VS Code Server from being retrieved during codespace startup. The impact was mitigated by implementing a workaround to use an alternative download path when the primary endpoint is degraded. We are working with the upstream dependency to address the root cause of the download service failure, and we are improving our fallback mechanisms to reduce the impact of similar upstream failures in the future.

We are investigating reports of degraded performance for Codespaces

We're investigating an issue where extensions fail to install in newly created Codespaces. Users can still create and access Codespaces, but extensions will not be operational, resulting in a degraded development experience. Our team is actively working to identify and resolve the root cause. We'll post another update by 14:00 UTC.

We are continuing to investigate an issue where extensions fail to install in newly created Codespaces. Users can create and access Codespaces, but extensions will not be operational, resulting in a degraded experience. The team is working on a fix. All newly created Codespaces are affected. We'll post another update by 15:00 UTC.

We have deployed a fix for the issue affecting extension installation in newly created Codespaces. New Codespaces are now being created with working extensions. We'll post another update by 15:30 UTC.

We're seeing partial recovery for the issue affecting extension installation in newly created Codespaces. Some users may still experience degraded functionality where extensions hit errors. The team continues to investigate the root cause while monitoring the recovery.

We're seeing intermittent failures downloading from the extension marketplace from codespaces and are investigating.

We're seeing intermittent failures downloading from the extension marketplace from codespaces, caused by IP blocks for some codespaces. We're working to remove those blocks.

Codespaces IPs are no longer being blocked from Visual Studio Marketplace operations and we are monitoring for full recovery

On March 12, 2026, between 01:00 UTC and 18:53 UTC, users saw failures downloading extensions within created or resumed codespaces. Users would see an error when attempting to use an extension within VS Code. Active codespaces with extensions already downloaded were not impacted. The extensions download failures were the result of a change introduced in our extension dependency and was resolved by updating the configuration of how those changes affect requests from Codespaces. We are enhancing observability and alerting of critical issues within regular codespace operations to better detect and mitigate similar issues in the future.

We are investigating reports of degraded performance for Codespaces

We are seeing about 5% of new Codespace creation requests failing. We are investigating the root cause and identifying the impacted regions.

We are seeing recovery, with the failure rate for new Codespace creation requests dropping from 5% to about 3%.

This incident has been resolved. New Codespace creation requests are now completing successfully.

On March 9, 2026, between 01:23 UTC and 03:25 UTC, users attempting to create or resume codespaces in the Australia East region experienced elevated failures, peaking at a 100% failure rate for this region. Codespaces in other regions were not affected. The create and resume failures were caused by degraded network connectivity between our control plane services and the VMs hosting the codespaces. This was resolved by redirecting traffic to an alternate site within the region. While we are addressing the core network infrastructure issue, we have also improved our observability of components in this area to improve detection. This will also enable our existing automated failovers to cover this failure mode. These changes will prevent or significantly reduce the time any similar incident causes user impact.