Part of GitHub

GitHub Codespaces Outage History

GitHub Codespaces is up right now

GitHub Codespaces had 7 outages in the last 2 years totaling 15h 28m of downtime — averaging 0.3 incidents per month.

There were 7 GitHub Codespaces outages since March 3, 2026 totaling 15h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.githubstatus.com

Minor July 14, 2026

Disruption with some GitHub services

Detected by Pingoru
Jul 14, 2026, 08:21 AM UTC
Resolved
Jul 14, 2026, 09:56 AM UTC
Duration
1h 35m
Affected: Codespaces
Timeline · 4 updates
  1. investigating Jul 14, 2026, 08:21 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Jul 14, 2026, 08:22 AM UTC

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

  3. monitoring Jul 14, 2026, 09:51 AM UTC

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

  4. resolved Jul 14, 2026, 09:56 AM UTC

    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.

Read the full incident report →

Minor April 23, 2026

Investigating errors on GitHub

Detected by Pingoru
Apr 23, 2026, 02:40 PM UTC
Resolved
Apr 23, 2026, 03:18 PM UTC
Duration
38m
Affected: ActionsPackagesCodespacesCopilot
Timeline · 8 updates
  1. investigating Apr 23, 2026, 02:40 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Apr 23, 2026, 02:41 PM UTC

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

  3. investigating Apr 23, 2026, 02:42 PM UTC

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

  4. investigating Apr 23, 2026, 02:44 PM UTC

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

  5. investigating Apr 23, 2026, 02:51 PM UTC

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

  6. investigating Apr 23, 2026, 03:02 PM UTC

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

  7. monitoring Apr 23, 2026, 03:02 PM UTC

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

  8. resolved Apr 23, 2026, 03:18 PM UTC

    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.

Read the full incident report →

Major April 16, 2026

Incident with Codespaces

Detected by Pingoru
Apr 16, 2026, 03:06 PM UTC
Resolved
Apr 16, 2026, 06:28 PM UTC
Duration
3h 21m
Affected: Codespaces
Timeline · 7 updates
  1. investigating Apr 16, 2026, 03:06 PM UTC

    We are investigating reports of degraded performance for Codespaces

  2. investigating Apr 16, 2026, 03:08 PM UTC

    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.

  3. investigating Apr 16, 2026, 03:41 PM UTC

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

  4. investigating Apr 16, 2026, 03:49 PM UTC

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

  5. investigating Apr 16, 2026, 04:37 PM UTC

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

  6. monitoring Apr 16, 2026, 06:22 PM UTC

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

  7. resolved Apr 16, 2026, 06:28 PM UTC

    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.

Read the full incident report →