Incident with Codespaces

Resolved

On April 11 from 3:05am UTC to 3:44am UTC, approximately 75% of Codespaces users faced create and start failures. These were caused by manual configuration changes to an internal dependency. We reverted the changes and immediately restored service health.We are working on safer mechanisms for testing and rolling out such configuration changes, and we expect no further disruptions.

Investigating

We have reverted a problematic configuration change and are seeing recovery across starts and resumes

Investigating

We have identified an issue that is causing errors when starting new and resuming existing Codespaces. We are currently working on a mitigation

Investigating

We are investigating reports of degraded availability for Codespaces