Incident with Git Operations
At a glance · GitHub's status
ResolvedLasted 51 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Git operations
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported degraded service affecting GitHub Git operations, starting 15:16 UTC on 22 Oct 2023. GitHub marked it resolved at 16:07 UTC after 51 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.
22 Oct 2023
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+52 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 Git operations
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 have mitigated the cause of the issue and are awaiting positive confirmation from impacted customers that the issue is fully resolved.
Investigating ·
We are currently investigating reports from some customers encountering errors when cloning repositories via workflows or via the command line.
Investigating ·
We are investigating reports of degraded performance for Git Operations
Last updated