Incident on 2016-05-24 19:55:07 UTC

At a glance · GitHub's status

ResolvedLasted under a minute

First posted
on GitHub Status
Ended
· marked resolved
Edited
Not since we first saw it
Source
GitHub Status · checked 1 min ago

In short

GitHub reported degraded service affecting GitHub, starting 19:55 UTC on 24 May 2016. GitHub marked it resolved at 19:55 UTC after under a minute.

GitHub says

GitHub's latest update, , in short excerpts.

<ul><li><strong>2016-05-24 19:55:07</strong> - We are investigating reports of delayed notifications.</li><li><strong>2016-05-24 22:11:14</strong> - Everything operating normally.</li></ul>

GitHub,

Read the full update on GitHub's status page

Timeline

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

  1. 24 May 2016

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

  2. 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 ·

    <ul><li><strong>2016-05-24 19:55:07</strong> - We are investigating reports of delayed notifications.</li><li><strong>2016-05-24 22:11:14</strong> - Everything operating normally.</li></ul>

Read the full update on GitHub's status page

Last updated