← Back to GitHub History
major✓ Resolved

Incident with Codespaces

GitHubThu, Apr 16, 2026, 03:06 PM
Status
resolved
Duration
3h 23m
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedThu, Apr 16, 2026, 06:30 PM
This incident has been resolved.
monitoringThu, Apr 16, 2026, 06:22 PM
The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
investigatingThu, Apr 16, 2026, 04:37 PM
Our provider is implementing a mitigation and we are seeing signs of recovery.
investigatingThu, Apr 16, 2026, 03:49 PM
We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.
investigatingThu, Apr 16, 2026, 03:41 PM
Codespaces is experiencing degraded availability. We are continuing to investigate.
investigatingThu, Apr 16, 2026, 03:08 PM
We are experiencing degraded performance in Codespaces related to creating a new Codespace or starting an existing Codespace from the VS Code editor. SSH connections to Codespaces are not impacted. We are working toward mitigation and will continue to keep you updated on progress.
investigatingThu, Apr 16, 2026, 03:06 PM
We are investigating reports of degraded performance for Codespaces

📊 TECHNICAL DETAILS

Internal ID
9c23550d-d327-47fd-9eea-8aa4a91ee8c5
External ID
bjyfg0yz1lwj
🕐 Started
Thu, Apr 16, 2026, 03:06 PM
🔄 Last Updated
Thu, Apr 16, 2026, 06:30 PM
✓ Resolved
Thu, Apr 16, 2026, 06:30 PM
MAJOR
Impact Level
3h 23m
Total Duration
6
Status Updates
Affected Components
Codespaces
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed