Degradation in repos contents API
At a glance · GitHub's status
ResolvedLasted 21 min
- 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 22:02 UTC on 4 Sep. GitHub marked it resolved at 22:23 UTC after 21 min.
GitHub says
GitHub's latest update, , in short excerpts.
On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations.
Timeline
Times in UTC, GitHub's own where it gives them.
4 Sep
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+21 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 September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations.
Investigating ·
We are investigating reports of impacted performance for some GitHub services.
Last updated