Incident on 2020-02-27 14:31 UTC
At a glance · GitHub's status
ResolvedLasted 4 h 22 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 14:31 UTC on 27 Feb 2020. GitHub marked it resolved at 18:54 UTC after 4 h 22 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.
27 Feb 2020
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+4 h 23 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 ·
Error rates across GitHub.com have now subsided and we continue to monitor recovery.
Investigating ·
We continue to investigate the issues with GitHub services and will shift to a slower update cadence to provide more meaningful updates going forward.
Investigating ·
We continue to investigate the source of increased errors affecting GitHub.com services.
Investigating ·
We are continuing to investigate elevated error rates across GitHub.com and will provide updates when we have them.
Investigating ·
We are investigating reports of increased API errors and webhook latency.
Last updated