CompaniesGitHub CopilotIncidents
GitHub Copilot: Disruption connecting to Codespaces
Timeline of updates
- resolved
On January 14, 2025, between 19:13 UTC and 21:210 UTC the Codespaces service was degraded and led to connection failures with running codespaces, with a 7.6% failure rate for connections during the degradation. Users with bad connections could not use impacted codespaces until they were stopped and restarted. This was caused by bad connections left behind after a deployment in an upstream dependency that the Codespaces service still provided to clients. The incident self-mitigated as new connections replaced stale ones. We are coordinating to ensure connection stability with future deployments of this nature.
From GitHub Copilot’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub Copilot, started 2025-01-14 20:55 UTC, resolved after 25 min, 1 update(s).
- Title
- Disruption connecting to Codespaces
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/bll83wkgdd2m
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on January 14, 2025GitHub Copilot in January 2025MarkdownJSON