Part of GitHub

Is GitHub Codespaces down?

Last checked 119d ago
Current status
GitHub Codespaces is up

No incidents right now.

Official status page: https://www.githubstatus.com · Polled every 5 minutes · 1 component tracked

GitHub Codespaces is operational right now. Last checked 119d ago; the most recent incident resolved 61d ago.

Real-time GitHub Codespaces status, recent outages, and incident history — pulled directly from GitHub Codespaces's official status page at https://www.githubstatus.com every 5 minutes. Pingoru tracks 1 GitHub Codespaces service and has captured 2 incidents in the last 90 days (97.78% uptime). Get email, Slack, Discord, or webhook alerts the moment GitHub Codespaces reports a new incident — free for 5 monitors, no credit card.

Users who monitor GitHub Codespaces also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
GitHub Codespaces uptime 97.78% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 35m
    Started Jul 14, 2026, 08:21 AM UTC · Resolved Jul 14, 2026, 09:56 AM UTC
    Codespaces
    Timeline · 4 updates
    • investigating · Jul 14, 2026, 08:21 AM UTC

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

    • investigating · Jul 14, 2026, 08:22 AM UTC

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

    • monitoring · Jul 14, 2026, 09:51 AM UTC

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

    • 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.

    Latest: 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.

  2. Resolved 2h 2m
    Started Jul 07, 2026, 02:14 PM UTC · Resolved Jul 07, 2026, 04:17 PM UTC
    ActionsCodespaces
    Timeline · 9 updates
    • investigating · Jul 07, 2026, 02:14 PM UTC

      We are investigating reports of degraded performance for Actions and Codespaces

    • 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.

    • investigating · Jul 07, 2026, 02:32 PM UTC

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

    • 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.

    • 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.

    • 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.

    • investigating · Jul 07, 2026, 04:00 PM UTC

      We have rolled out the mitigation and are seeing recovery.

    • monitoring · Jul 07, 2026, 04:02 PM UTC

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

    • 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.

    Latest: 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.

Outage history

Past 90 days · 2 incidents View full outage history →