Incident on 2019-10-02 16:10 UTC

At a glance · GitHub's status

ResolvedLasted 3 h 19 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 16:23 UTC on 2 Oct 2019. GitHub marked it resolved at 19:42 UTC after 3 h 19 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. 2 Oct 2019

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

  2. +13 min

    GitHubGitHub says it startedon GitHub Status

  3. +3 h 32 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 are continuing to monitor the repairs to affected repositories.

  3. Investigating ·

    The majority of repo forks are complete, we are monitoring the remaining ones.

  4. Investigating ·

    We continue to monitor the backlog of repo forks.

  5. Investigating ·

    We are continuing to work through the fork backlog.

  6. Investigating ·

    We are continuing to monitor the repo fork backlog.

  7. Investigating ·

    We are currently processing the backlog of repo forks.

  8. Investigating ·

    The issue with creating forks has been resolved, requested forks are being processed.

  9. Investigating ·

    The issue with creating forks has been resolved, requested forks are being processed.

  10. Investigating ·

    Currently investigating issues affecting some users when attempting to fork repositories.

Read the full update on GitHub's status page

Last updated