Part of GitHub

GitHub Codespaces Outage History

GitHub Codespaces is up right now

Pingoru has recorded 8 incidents for GitHub Codespaces: 8 in the last 12 months and 0 in the last 90 days.

Source: githubstatus.com

8incidents recorded
8last 12 months
0last 90 days
2 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking GitHub Codespaces in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202624 of 720 (1%)
May 202611 of 744 (0%)
June 202600 of 720 (0%)
July 202624 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 724 (0%)

Incidents, newest first

Minor July 14, 2026 Disruption with some GitHub services 1h 35m Codespaces

Started Jul 14, 2026, 08:21 AM UTC· resolved Jul 14, 2026, 09:56 AM UTC

  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 →

Major July 7, 2026 Actions and Codespaces APIs experiencing partial failures 2h 2m Actions, Codespaces

Started Jul 07, 2026, 02:14 PM UTC· resolved Jul 07, 2026, 04:17 PM UTC

  1. investigating Jul 07, 2026, 02:14 PM UTC

    We are investigating reports of degraded performance for Actions and Codespaces

  2. investigating Jul 07, 2026, 02:14 PM UTC

    Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time. Actions runs in progress are continuing successfully.

  3. investigating Jul 07, 2026, 02:32 PM UTC

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

  4. investigating Jul 07, 2026, 02:47 PM UTC

    Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time. Retries may be successful. Actions runs and codespaces in progress are continuing successfully. We are continuing to investigate the source of these errors.

  5. investigating Jul 07, 2026, 03:06 PM UTC

    Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful. We continue to investigate the source of these errors.

  6. investigating Jul 07, 2026, 03:50 PM UTC

    Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation.

  7. investigating Jul 07, 2026, 04:00 PM UTC

    We have rolled out the mitigation and are seeing recovery.

  8. monitoring Jul 07, 2026, 04:02 PM UTC

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

  9. resolved Jul 07, 2026, 04:17 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 →

Critical May 4, 2026 Incident with Issues and Webhooks 54m Git Operations, Webhooks, Issues, Pull Requests and 4 more

Started May 04, 2026, 03:45 PM UTC· resolved May 04, 2026, 04:40 PM UTC

  1. investigating May 04, 2026, 03:45 PM UTC

    We are investigating reports of degraded performance for Issues and Webhooks

  2. investigating May 04, 2026, 03:48 PM UTC

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

  3. investigating May 04, 2026, 03:48 PM UTC

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

  4. investigating May 04, 2026, 03:50 PM UTC

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

  5. investigating May 04, 2026, 03:51 PM UTC

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

  6. investigating May 04, 2026, 03:51 PM UTC

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

  7. investigating May 04, 2026, 03:56 PM UTC

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

  8. investigating May 04, 2026, 04:05 PM UTC

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

  9. investigating May 04, 2026, 04:06 PM UTC

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

  10. investigating May 04, 2026, 04:25 PM UTC

    Git Operations is operating normally.

  11. investigating May 04, 2026, 04:28 PM UTC

    Actions and Packages are operating normally.

  12. investigating May 04, 2026, 04:29 PM UTC

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

  13. investigating May 04, 2026, 04:29 PM UTC

    Pages is operating normally.

  14. investigating May 04, 2026, 04:32 PM UTC

    Pull Requests is operating normally.

  15. investigating May 04, 2026, 04:34 PM UTC

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

  16. investigating May 04, 2026, 04:35 PM UTC

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

  17. investigating May 04, 2026, 04:35 PM UTC

    Webhooks is operating normally.

  18. monitoring May 04, 2026, 04:36 PM UTC

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

  19. resolved May 04, 2026, 04:40 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 →

Minor April 23, 2026 Investigating errors on GitHub 38m Actions, Packages, Codespaces, Copilot

Started Apr 23, 2026, 02:40 PM UTC· resolved Apr 23, 2026, 03:18 PM UTC

  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 3h 21m Codespaces

Started Apr 16, 2026, 03:06 PM UTC· resolved Apr 16, 2026, 06:28 PM UTC

  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 →

Minor March 12, 2026 Degraded Codespaces experience 5h 46m Codespaces

Started Mar 12, 2026, 01:06 PM UTC· resolved Mar 12, 2026, 06:53 PM UTC

  1. investigating Mar 12, 2026, 01:06 PM UTC

    We are investigating reports of degraded performance for Codespaces

  2. investigating Mar 12, 2026, 01:07 PM UTC

    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.

  3. investigating Mar 12, 2026, 01:50 PM 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.

  4. investigating Mar 12, 2026, 02:29 PM 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.

  5. investigating Mar 12, 2026, 03:08 PM 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.

  6. investigating Mar 12, 2026, 04:09 PM UTC

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

  7. investigating Mar 12, 2026, 05:20 PM UTC

    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.

  8. investigating Mar 12, 2026, 05:59 PM UTC

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

  9. resolved Mar 12, 2026, 06:53 PM UTC

    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.

Read the full incident report →

Major March 3, 2026 Incident with all GitHub services 1h 9m Git Operations, Webhooks, API Requests, Issues and 4 more

Started Mar 03, 2026, 06:59 PM UTC· resolved Mar 03, 2026, 08:09 PM UTC

  1. investigating Mar 03, 2026, 06:59 PM UTC

    We are investigating reports of degraded availability for Actions, Copilot and Issues

  2. investigating Mar 03, 2026, 07:00 PM UTC

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

  3. investigating Mar 03, 2026, 07:00 PM UTC

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

  4. investigating Mar 03, 2026, 07:02 PM UTC

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

  5. investigating Mar 03, 2026, 07:03 PM UTC

    We're seeing some service degradation across GitHub services. We're currently investigating impact.

  6. investigating Mar 03, 2026, 07:04 PM UTC

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

  7. investigating Mar 03, 2026, 07:05 PM UTC

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

  8. investigating Mar 03, 2026, 07:11 PM UTC

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

  9. investigating Mar 03, 2026, 07:14 PM UTC

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

  10. investigating Mar 03, 2026, 07:15 PM UTC

    API Requests is operating normally.

  11. investigating Mar 03, 2026, 07:17 PM UTC

    We've identified the issue and have applied a mitigation. We're seeing recovery of services. We continue to montitor for full recovery.

  12. investigating Mar 03, 2026, 07:23 PM UTC

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

  13. investigating Mar 03, 2026, 07:24 PM UTC

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

  14. investigating Mar 03, 2026, 07:25 PM UTC

    Codespaces is operating normally.

  15. investigating Mar 03, 2026, 07:25 PM UTC

    Webhooks is operating normally.

  16. investigating Mar 03, 2026, 07:27 PM UTC

    Issues is operating normally.

  17. investigating Mar 03, 2026, 07:28 PM UTC

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

  18. investigating Mar 03, 2026, 07:31 PM UTC

    Pull Requests is operating normally.

  19. investigating Mar 03, 2026, 07:31 PM UTC

    Copilot is operating normally.

  20. investigating Mar 03, 2026, 07:33 PM UTC

    We are seeing recovery across multiple services. Impact is mostly isolated to git operations at this point, we continue to investigate

  21. investigating Mar 03, 2026, 07:36 PM UTC

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

  22. investigating Mar 03, 2026, 07:54 PM UTC

    Git Operations is operating normally.

  23. investigating Mar 03, 2026, 07:55 PM UTC

    Actions is operating normally.

  24. investigating Mar 03, 2026, 08:06 PM UTC

    We're seeing recovery across all services. We're continuing to monitor for full recovery.

  25. resolved Mar 03, 2026, 08:09 PM UTC

    On March 3, 2026, between 18:46 UTC and 20:09 UTC, GitHub experienced a period of degraded availability impacting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other dependent services. At the peak of the incident, GitHub.com request failures reached approximately 40%. During the same period, approximately 43% of GitHub API requests failed. Git operations over HTTP had an error rate of approximately 6%, while SSH was not impacted. GitHub Copilot requests had an error rate of approximately 21%. GitHub Actions experienced less than 1% impact. This incident shared the same underlying cause as an incident in early February where we saw a large volume of writes to the user settings caching mechanism. While deploying a change to reduce the burden of these writes, a bug caused every user’s cache to expire, get recalculated, and get rewritten. The increased load caused replication delays that cascaded down to all affected services. We mitigated this issue by immediately rolling back the faulty deployment. We understand these incidents disrupted the workflows of developers. While we have made substantial, long-term investments in how GitHub is built and operated to improve resilience, we acknowledge we have more work to do. Getting there requires deep architectural work that is already underway, as well as urgent, targeted improvements. We are taking the following immediate steps: - We have added a killswitch and improved monitoring to the caching mechanism to ensure we are notified before there is user impact and can respond swiftly. - We are moving the cache mechanism to a dedicated host, ensuring that any future issues will solely affect services that rely on it.

Read the full incident report →