‹ Back to incident history

Incident with Pull Requests, Git Operations and Issues

ResolvedMajor outageGitHub
Wednesday, November 4, 2026 17:49 – Wednesday, November 4, 2026 19:50 (2 hr)
Affected components
Git Operations
API Requests
Issues
Pull Requests
Actions
Updates
ResolvedWednesday, November 4, 2026 19:50

n 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.<br /><br />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.<br /><br />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.

MonitoringWednesday, November 4, 2026 19:43

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

InvestigatingWednesday, November 4, 2026 19:30

The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

InvestigatingWednesday, November 4, 2026 19:17

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.

InvestigatingWednesday, November 4, 2026 19:11

API Requests is experiencing degraded performance. We are continuing to investigate.

InvestigatingWednesday, November 4, 2026 18:38

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.

InvestigatingWednesday, November 4, 2026 17:53

Pull Requests is experiencing degraded availability. We are continuing to investigate.

InvestigatingWednesday, November 4, 2026 17:50

Actions is experiencing degraded performance. We are continuing to investigate.

InvestigatingWednesday, November 4, 2026 17:49

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

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview