Incident with Actions, Pull Requests and Issues
Incident
Report for GitHub
Resolved
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.
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.
Update
Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
Update
Web and email notifications continue to be delayed as we work through a backlog of notifications.
Update
Notifications have resumed but will continue to be delayed as we work through a backlog.
Update
We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
Update
We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
Update
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Update
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Update
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.
Update
Pull Requests is operating normally.
Update
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
Update
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.
Investigating
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
This incident affected: Issues, Pull Requests, and Actions.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe