Incident with Codespaces
At a glance · GitHub's status
ResolvedLasted 1 h 40 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Codespaces
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked 14 min ago
In short
GitHub reported degraded service affecting GitHub Codespaces, starting 00:07 UTC on 31 Dec 2022. GitHub marked it resolved at 01:47 UTC after 1 h 40 min.
GitHub says
GitHub's latest update, , in short excerpts.
This incident has been resolved.
Timeline
Times in UTC, GitHub's own where it gives them.
31 Dec 2022
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+1 h 41 min
GitHubResolved
What GitHub changed
GitHub adds updates to its incidents. We save every version (checked every minute) and list what changed. Quotes are short excerpts. The full text is on GitHub's page.
One version so far. If GitHub edits it, each change shows here with what was removed and added.
First version we captured ·
As first seen: resolved · 1 service
- Status
- resolved
- Services
- GitHub Codespaces
Seen by us · GitHub's timestamp · GitHub's page
Affected services
Official updates
Posted by GitHub Status, newest first. The newest are quoted in their first sentence; the full text of each is on GitHub's page.
Resolved ·
This incident has been resolved.
Investigating ·
We are continuing mitigation for an issue impacting some Codespaces customers.
Investigating ·
We are continuing to work on mitigation for an issue impacting some Codespaces customers.
Investigating ·
We identified an issue that impacts some Codespaces customers and are working on mitigation.We will continue to keep you updated on progress.
Investigating ·
We are investigating reports of degraded performance for Codespaces.
Last updated