GitHub outage on October 12, 2026: Incident with Actions, Pull Requests and Issues
GitHub reported an incident affecting GitHub for 7 hours 54 minutes on 12 October 2026, from 12:21 to 20:16 UTC.
Resolved
Official incident reported by GitHub
- Started
- 12:21
- 12 Oct 2026 UTC
- Resolved
- 20:16
- 12 Oct 2026 UTC
- Duration
- 7h 54m
- 7 hours 54 minutes
- Impact
- Minor
- as rated by GitHub
- Updates
- 13
- posted by GitHub
Timeline
All times UTC.
Official incident from GitHub
Incident with Actions, Pull Requests and Issues
-
Official
Investigating
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
-
Official
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.
-
Official
Investigating
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
-
Official
Investigating
Pull Requests is operating normally.
-
Official
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.
-
Official
Investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
-
Official
Investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
Official
Investigating
We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
-
Official
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.
-
Official
Investigating
Notifications have resumed but will continue to be delayed as we work through a backlog.
-
Official
Investigating
Web and email notifications continue to be delayed as we work through a backlog of notifications.
-
Official
Investigating
Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
-
Official
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.
"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.
Does your product depend on GitHub?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.