- Level
- confirmed
- Worst impact
- Degraded
- Components
- Issues, Pull Requests, Actions
- Down Index
- 42of 100
What to do
Check whether you use GitHub Actions 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 Actions's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-actions works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub Actions 13
- investigating
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
provider
- investigating
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
- investigating
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
provider
- investigating
Pull Requests is operating normally.
provider
- investigating
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
- investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
provider
- investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
provider
- investigating
We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
provider
- investigating
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
- investigating
Notifications have resumed but will continue to be delayed as we work through a backlog.
provider
- investigating
Web and email notifications continue to be delayed as we work through a backlog of notifications.
provider
- investigating
Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-84e07c9610
Is GitHub Actions still down?
No, this incident was resolved 2026-10-12 20:16 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.
How long did it last?
7h 54m, from 2026-10-12 12:21 UTC to 2026-10-12 20:16 UTC, by the times GitHub Actions posted.
What was affected?
GitHub Actions named Issues, Pull Requests, Actions.
What caused it?
GitHub Actions hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub Actions's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.