Incident on 2020-04-28 16:44 UTC
At a glance · GitHub's status
ResolvedLasted 58 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 16:44 UTC on 28 Apr 2020. GitHub marked it resolved at 17:42 UTC after 58 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.
28 Apr 2020
GitHubFirst public postFrom GitHub's own incident history, before our archive started.
+58 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 ·
We have identified the problem with the cache action, and are working on a fix.
Investigating ·
We are investigating elevated errors with GitHub Actions workflows using the cache action.
Last updated