MicrosoftRadarIndependent status for Microsoft services

Disruption with GitHub services

ResolvedResolved1 version

Facts

Source
GitHub Status · original
Started
(14 days ago)
Ended
· lasted 32 min
How it ended
Microsoft marked it resolved.
First captured by us
Last changed
(43 min ago)
Affected services
GitHub Issues, GitHub Pages

Last text from Microsoft

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Quoted from GitHub Status (source), captured . Reproduced for reporting and archival purposes.

Official updates

Posted by GitHub Status, newest first.

  1. Resolved

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  2. Monitoring

    The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

  3. Investigating

    A temporarily overloaded component triggered a burst of errors between 14:21 and 14:30 UTC across numerous services. Component health has returned to normal and we continue to monitor while investigating the root cause.<br />

  4. Investigating

    Issues is operating normally.

  5. Investigating

    Pages is experiencing degraded performance. We are continuing to investigate.

  6. Investigating

    Issues is experiencing degraded performance. We are continuing to investigate.

  7. Investigating

    We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation.

  8. Investigating

    We are investigating reports of impacted performance for some GitHub services.

What Microsoft changed

Microsoft edits the text of an incident in place. We keep every version we capture (checked every minute) and highlight the difference. Removed text is struck through, added text is marked.

  1. First version we captured

    Captured · Microsoft's own timestamp · revision kw3pxydw
    Original text as we first saw it

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.