Incidentsby GlyphIncident with Codespaces
Feb 12, 07:53 UTCFeb 12, 09:56 UTC
Duration
2h 3m
Impact
Major
Root cause
Deployment
GitHub, 90 days
69 incidents
Affected
Not listed by the vendor.
Lesson: Teams should monitor cloud development environments to quickly detect service incidents.
What happened
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.
Timeline
- Resolved · Feb 12, 09:56 UTC
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.