MicrosoftRadar Independent status for Microsoft services

Incident on 2020-05-22 16:41 UTC

At a glance · GitHub's status

ResolvedLasted 2 h 44 min

GitHub says it started
· on GitHub Status
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 00:30 UTC on 23 May 2020. GitHub marked it resolved at 03:14 UTC after 2 h 44 min.

GitHub says

GitHub's latest update, , in short excerpts.

This incident has been resolved.

GitHub,

Read the full update on GitHub's status page

Timeline

Times in UTC, GitHub's own where it gives them.

  1. 22 May 2020

    GitHubFirst public postFrom GitHub's own incident history, before our archive started.

  2. 23 May 2020+7 h 49 min

    GitHubGitHub says it startedon GitHub Status

  3. +10 h 33 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.

  1. 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.

  1. Resolved ·

    This incident has been resolved.

  2. Investigating ·

    We have remediated the increase in errors on GitHub.com.

  3. Investigating ·

    We continue to monitor the remediation of elevated errors on GitHub.com.

  4. Investigating ·

    We have resolved the issue that resulted in occasional stale data on GitHub.com.

  5. Investigating ·

    We are still monitoring the remediation and will provide another update in 1 hour.

  6. Investigating ·

    We continue to monitor the remediation and will provide the next update in 1 hour.

  7. Investigating ·

    The last incident update was due to the ongoing remediation work.

  8. Investigating ·

    We are also investigating elevated error rates for GitHub.com.

  9. Investigating ·

    We continue to monitor the remediation and will provide the next update in 1 hour.

  10. Investigating ·

    We have identified the source causing elevated errors as well as occasional stale data on GitHub.com.

  11. Investigating ·

    We continue to investigate an increase in errors on GitHub.com.

  12. Investigating ·

    We are investigating an increase in errors on GitHub.com.

Read the full update on GitHub's status page

Last updated