CompaniesGitHub CopilotIncidents
GitHub Copilot: Incident with Codespaces
Timeline of updates
- resolved
On July 18, 2024, from 22:37 UTC to 04:47 UTC, one of our provider's services experienced degradation, causing errors in Codespaces, particularly when starting the VSCode server and installing extensions. The error rate reached nearly 100%, resulting in a global outage of Codespaces. During this time, users worldwide were unable to connect to VSCode. However, other clients that do not rely on the VSCode server, such as GitHub CLI, remained functional. We are actively working to enhance our detection and mitigation processes to improve our response time to similar issues in the future. Additionally, we are exploring ways to operate Codespaces in a more degraded state when one of our providers encounters issues, to prevent a complete outage.
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 2024-07-19 02:10 UTC, resolved after 2.6 h, 1 update(s).
- Title
- Incident with Codespaces
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/9rrqvvf23fhc
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on July 19, 2024GitHub Copilot in July 2024MarkdownJSON