We are investigating reports of degraded performance.
At a glance · GitHub's status
ResolvedLasted under a minute
- GitHub says it started
- · on GitHub Status
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported degraded service affecting GitHub, starting 11:34 UTC on 15 Nov 2023. GitHub marked it resolved at 11:34 UTC after under a minute.
GitHub says
GitHub's latest update, , in short excerpts.
On 2023-11-15, from 09:44 to 10:42 UTC, some GitHub customers experienced increased latency or errors accessing repo data.<br /><br />High concurrent access to a specific…
Timeline
Times in UTC, GitHub's own where it gives them.
15 Nov 2023
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+1 h 43 min
GitHubGitHub says it startedon GitHub Status
+1 h 43 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
- Status
- resolved
Seen by us · GitHub's timestamp · GitHub's page
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 ·
On 2023-11-15, from 09:44 to 10:42 UTC, some GitHub customers experienced increased latency or errors accessing repo data.<br /><br />High concurrent access to a specific…
Investigating ·
Error rates and performance have returned to normal.
Investigating ·
We have identified the source of the issue and have removed the additional load from the service.
Investigating ·
We are seeing connectivity issues between some of our systems and git backend services.
Investigating ·
We are currently investigating this issue.
Last updated