Incident with Git Operations, Issues and Pull Requests
At a glance · GitHub's status
ResolvedLasted 52 min
- First posted
- on GitHub Status
- Ended
- · marked resolved
- Affects
- GitHub Git operations, GitHub pull requests, GitHub Issues
- Edited
- Not since we first saw it
- Source
- GitHub Status · checked just now
In short
GitHub reported degraded service affecting GitHub Git operations, GitHub pull requests and GitHub Issues, starting 01:16 UTC on 31 Mar 2023. GitHub marked it resolved at 02:08 UTC after 52 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.
31 Mar 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 · 3 services
- Status
- resolved
- Services
- GitHub Git operations, GitHub pull requests, GitHub Issues
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 identified the issue and are deploying a fix.
Investigating ·
Issues and Pull Requests are experiencing degraded performance.
Investigating ·
We are investigating reports of degraded performance for Git Operations.
Last updated