Minor impactResolvedDevOps

GitHub incident: Incident with Actions, Pull Requests and Issues

GitHub reported this minor-impact incident on its official status page on Oct 12, 2026, 12:21 UTC. It was resolved after 7h 54m.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Oct 12, 2026, 12:21 UTC
started
Oct 12, 2026, 20:16 UTC
resolved
7h 54m
duration
Minor
impact

Affected components

  • Actions
  • Issues
  • Pull Requests
  1. resolvedOct 12, 2026, 20:16 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. <br /><br />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. <br /><br />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.<br /><br />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

  2. investigatingOct 12, 2026, 19:28 UTC

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

  3. investigatingOct 12, 2026, 17:34 UTC

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

  4. investigatingOct 12, 2026, 15:50 UTC

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

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

  6. investigatingOct 12, 2026, 14:37 UTC

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

  7. investigatingOct 12, 2026, 14:36 UTC

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

  8. investigatingOct 12, 2026, 14:35 UTC

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

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

  10. investigatingOct 12, 2026, 13:02 UTC

    Pull Requests is operating normally.

  11. investigatingOct 12, 2026, 12:57 UTC

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

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

  13. investigatingOct 12, 2026, 12:21 UTC

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

What APIStatus.watch saw

  • Oct 12, 2026, 12:22 UTCoperational → degraded
  • Oct 12, 2026, 14:37 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 63 incidents in the last 90 days, 23 of them major or critical. A typical incident lasted 1h 11m. See GitHub's uptime and incident history