MicrosoftRadarIndependent status for Microsoft services

Project updates delayed

ResolvedResolved1 version

Facts

Source
GitHub Status · original
Started
(22 days ago)
Ended
· lasted 11 h 2 min
How it ended
Microsoft marked it resolved.
First captured by us
Last changed
(43 min ago)
Affected services
GitHub Actions, GitHub API requests, GitHub pull requests, GitHub Issues, GitHub Packages

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 has been mitigated. We are monitoring to ensure stability.

  3. Investigating

    GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. <br /><br />We're continuing to work on the remaining delays and monitor recovery.

  4. Investigating

    Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed.<br /><br />We have seen some recovery, and are working to add more capacity to accelerate the recovery.

  5. Investigating

    Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed.<br /><br />We've identified interruptions in update processing and are evaluating mitigations to restore normal operation.

  6. Investigating

    Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.

  7. Investigating

    Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.

  8. Investigating

    The other affected services have recovered. <br /><br />We're continuing to investigate GitHub Projects and verify that normal operation has been restored.

  9. Investigating

    We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.

  10. Investigating

    Actions, Issues, Packages and Pull Requests are operating normally.

  11. Investigating

    We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're continuing to work towards full recovery and monitoring for stability.

  12. Investigating

    Some users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com. <br /><br />We're working through multiple mitigation efforts and continuing to investigate.

  13. Investigating

    API Requests is operating normally.

  14. Investigating

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

  15. Investigating

    API Requests is experiencing degraded performance. We are continuing to investigate.

  16. Investigating

    Some users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're investigating and evaluating mitigation options to restore normal service.

  17. Investigating

    Some users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're investigating and working to restore normal service.

  18. Investigating

    We are investigating reports of degraded performance for Actions, Issues and Pull Requests

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