Incident with Actions, Pull Requests and Issues

Updates timeline

1. Investigating Oct 12, 12:21 PM UTC

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

2. Investigating Oct 12, 12:33 PM UTC

   Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.

3. Investigating Oct 12, 12:57 PM UTC

   We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.

4. Investigating Oct 12, 01:02 PM UTC

   Pull Requests is operating normally.

5. Investigating Oct 12, 01:38 PM UTC

   Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.

6. Investigating Oct 12, 02:35 PM UTC

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

7. Investigating Oct 12, 02:36 PM UTC

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

8. Investigating Oct 12, 02:37 PM UTC

   We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.

9. Investigating Oct 12, 03:19 PM UTC

   We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.

10. Investigating Oct 12, 03:50 PM UTC

    Notifications have resumed but will continue to be delayed as we work through a backlog.

11. Investigating Oct 12, 05:34 PM UTC

    Web and email notifications continue to be delayed as we work through a backlog of notifications.

12. Investigating Oct 12, 07:28 PM UTC

    Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.

13. Resolved Oct 12, 08:16 PM UTC

    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.