Investigating reports of degraded performance.
At a glance · GitHub's status
ResolvedLasted 1 h 10 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked 26 min ago
In short
GitHub reported an advisory affecting GitHub, starting 16:02 UTC on 30 Nov 2022. GitHub marked it resolved at 17:13 UTC after 1 h 10 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.
30 Nov 2022
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+1 h 11 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 ·
This incident has been resolved.
Investigating ·
The issue affecting the new code view beta has been resolved.
Investigating ·
We have diagnosed that the ongoing issue related to code search and code view is limited to customers in the current beta for those features.
Investigating ·
We are investigating reports of issues with service(s): GitHub Search and the new Code View.
Investigating ·
We are currently investigating this issue.
Last updated