Operational from 9:49 AM to 11:11 AM, Degraded performance from 9:50 AM to 11:43 AM, Operational from 11:30 AM to 11:50 AM
GitHub → Actions
Degraded performance from 9:50 AM to 11:43 AM, Operational from 11:43 AM to 11:50 AM
GitHub → API Requests
Operational from 9:49 AM to 11:11 AM, Degraded performance from 11:11 AM to 11:30 AM, Operational from 11:30 AM to 11:50 AM
·
Resolved · UTC
On November 4, 2026, between 09:35 UTC and 11:43 UTC, customers experienced intermittent errors and timeouts across GitHub.com, primarily on actions that write data. At peak, about 20% of pull request write operations (such as merging, commenting, and reviewing) failed, along with about 10% of issue creates and edits and 10–15% of project item edits. Git pushes over SSH, REST and GraphQL API requests, code scanning uploads, releases, and package operations were also affected, and about 1% of Actions runs were delayed by more than five minutes or failed to start. Overall, nearly 4% of all requests to GitHub.com failed at the worst point. Reads were largely unaffected, and retrying a failed action a short time later usually succeeded.
The incident was triggered by a burst of concurrent updates to the same database record, which tied up all available connections to one of our primary databases. Although that contention cleared, the backlog of waiting requests kept our database connection layer overloaded, and it did not recover on its own. We mitigated the incident by failing over to a new primary database host. Most services recovered by 11:31 UTC, and Actions recovered by 11:43 UTC.
Since the incident, we have disabled the code path that triggered the contention, increased the processing capacity of our database connection layer by 50%, and added alerting to detect this type of overload earlier. We are also improving our procedures so we can fail over sooner in similar situations.
Monitoring · UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Update · UTC
The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
Update · UTC
We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available.
Update · UTC
API Requests is experiencing degraded performance. We are continuing to investigate.
Update · UTC
We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation.
Update · UTC
Pull Requests is experiencing degraded availability. We are continuing to investigate.
Update · UTC
Actions is experiencing degraded performance. We are continuing to investigate.
Investigating · UTC
We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests