[2026-02-12] Incident Thread

[github-actions[bot]]

❗ An incident has been declared:

Incident with Codespaces

Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.

[github-actions[bot]]

Update

We are seeing an increase in Codespaces creation and resuming failures across multiple regions, primarily in EMEA. Our team are analysing the situation and are working to mitigate this impact.

While we are working, customers are advised to create Codespaces in US East and US West regions via the "New with options..." button when creating a Codespace.

More updates as we have them.

[smather-pm]

Go faster, this has been a problem now for 5+ hours.

[github-actions[bot]]

Update

We now understand the source of the VM create/resume failures and are working with our partners to mitigate the impact.

[github-actions[bot]]

Update

We have identified the issue causing Codespace create/resume actions to fail and are applying a fix. This is estimated to take ~2 hours to complete but impact will begin to reduce sooner than that.

We will continue to monitor recovery progress and will report back when more information is available.

[github-actions[bot]]

Update

We are seeing widespread recovery across all our regions.

We will continue to monitor progress and will resolve the incident when we are confident on durable recovery.

[github-actions[bot]]

Update

Recovery looks consistent with Codespaces creating and resuming successfully across all regions.

Thank you for your patience.

[github-actions[bot]]

Incident Resolved

This incident has been resolved.

[github-actions[bot]]

Incident Summary

On February 12, 2026, between 00:51 UTC and 09:35 UTC, users attempting to create or resume Codespaces experienced elevated failure rates across Europe, Asia and Australia, peaking at a 90% failure rate.

The disconnects were triggered by a bad configuration rollout in a core networking dependency, which led to internal resource provisioning failures. We are working to improve our alerting thresholds to catch issues before they impact customers and strengthening rollout safeguards to prevent similar incidents.