Incident with Actions, Pull Requests and Issues

What to do

• Check whether you use GitHub Issues, Pull Requests, Actions. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 7h 54m it lasted.

  Anything that failed between 2026-10-12 12:21 UTC and 2026-10-12 20:16 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 13

1. investigatingOct 12, 2026, 12:21 PM UTC

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

   provider

2. investigatingOct 12, 2026, 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.

   provider

3. investigatingOct 12, 2026, 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.

   provider

4. investigatingOct 12, 2026, 1:02 PM UTC

   Pull Requests is operating normally.

   provider

5. investigatingOct 12, 2026, 1: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.

   provider

6. investigatingOct 12, 2026, 2:35 PM UTC

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

   provider

7. investigatingOct 12, 2026, 2:36 PM UTC

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

   provider

8. investigatingOct 12, 2026, 2: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.

   provider

9. investigatingOct 12, 2026, 3: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.

   provider

10. investigatingOct 12, 2026, 3:50 PM UTC

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

    provider

11. investigatingOct 12, 2026, 5:34 PM UTC

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

    provider

12. investigatingOct 12, 2026, 7:28 PM UTC

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

    provider

13. resolvedOct 12, 2026, 8:16 PM UTC

    On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC. The incident was triggered through a latent condition in our notifications delivery pipeline that put a high volume of an expensive query on our sharded database replicas. This reduced available database capacity to serve requests for Issues, Pull Requests, Projects, and Actions. We have fixed the notifications pipeline’s code path that issued the expensive query. We are also improving resilience of the database layer to reduce the likelihood and impact of similar incidents.

    provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.