GitHub incident

Errors starting and connecting to Codespaces

Minor Resolved View vendor source →
Started
Mar 16, 2026, 03:01 PM UTC
Resolved
Mar 16, 2026, 03:28 PM UTC
Duration
27m
Detected by Pingoru
Mar 16, 2026, 03:01 PM UTC

Update timeline

  1. investigating Mar 16, 2026, 03:01 PM UTC

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

  2. investigating Mar 16, 2026, 03:06 PM UTC

    We are investigating reports of users experiencing errors when starting or connecting to Codespaces. Some users may be unable to access their development environments during this time. We are working to identify the root cause and will implement a fix as soon as possible.

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

    Errors starting or resuming Codespaces have resolved.

  4. resolved Mar 16, 2026, 03:28 PM UTC

    On 16 March 2026, between 14:16 UTC and 15:18 UTC, Codespaces users encountered a download failure error message when starting newly created or resumed codespaces. At peak, 96% of the created or resumed codespaces were impacted. Active codespaces with a running VSCode environment were not affected. The error was a result of an API deployment issue with our VS Code remote experience dependency and was resolved by rolling back that deployment. We are working with our partners to reduce our incident engagement time, improve early detection before they impact our customers, and ensure safe rollout of similar changes in the future.

Looking to track GitHub downtime and outages?

Pingoru polls GitHub's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GitHub reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GitHub alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GitHub for free

5 free monitors · No credit card required