Incident with Git Operations
At a glance · GitHub's status
ResolvedLasted 1 h 26 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Git operations
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked 28 min ago
In short
GitHub reported degraded service affecting GitHub Git operations, starting 22:39 UTC on 9 May 2023. GitHub marked it resolved at 00:06 UTC on 10 May 2023 after 1 h 26 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.
9 May 2023
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
10 May 2023+1 h 26 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 are seeing slower than usual times to run git clone over HTTPS.
Investigating ·
We are seeing slower than usual times to run git clone over HTTPS.
Investigating ·
We are investigating reports of degraded performance for Git Operations.
Last updated