Incident with Codespaces

What to do

• Check whether you use GitHub Codespaces. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 3h 21m it lasted.

  Anything that failed between 2026-04-16 15:06 UTC and 2026-04-16 18:28 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 7

1. investigatingApr 16, 2026, 3:06 PM UTC

   We are investigating reports of degraded performance for Codespaces

   provider

2. investigatingApr 16, 2026, 3: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.

   provider

3. investigatingApr 16, 2026, 3:41 PM UTC

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

   provider

4. investigatingApr 16, 2026, 3:49 PM UTC

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

   provider

5. investigatingApr 16, 2026, 4:37 PM UTC

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

   provider

6. monitoringApr 16, 2026, 6:22 PM UTC

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

   provider

7. resolvedApr 16, 2026, 6: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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.