GitHub incident of 16 Nov 2026: what happened and how long it lasted
GitHub’s incident of 16 Nov 2026 was open on GitHub’s status page for 4 h 27 min, from 11:59 to 16:26 UTC, and affected Pull Requests and Actions.
Last changed . Last checked . Source: stspg.io/ljtn69jlt087.
GitHub's updatesOldest first, in the vendor's own words. Times are UTC.
We are investigating reports of degraded performance for Pull Requests
We’re investigating elevated timeouts when merging pull requests. Some users may be unable to merge pull requests successfully; timeouts are occurring at a higher rate than usual. We’re working to identify the cause and restore normal performance.
We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. We’ll share another update as we learn more.
We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not restored normal performance, and our teams are continuing to investigate. We’ll share another update as we learn more.
We’re continuing to investigate elevated pull request merge timeouts. Approximately 3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not materially improved performance, and our teams are working to reduce load and restore normal service. We’ll share another update as we learn more.
We’re continuing to investigate elevated pull request merge timeouts. The latest reported rate is 4.75%, compared with a baseline near 0.2%, so some users may have difficulty merging pull requests. We’ll share another update as we learn more.
Actions is experiencing degraded performance. We are continuing to investigate.
We’re seeing early signs of improvement in pull request merge times, but recovery is not yet confirmed. The last confirmed timeout rate was 2.5%, compared with a baseline near 0.2%, so some users may still have difficulty merging pull requests. We’ll share another update as we learn more.
We’re seeing early signs of improvement in pull request merge times & workflow start times, but recovery is not yet confirmed. Users may still have difficulty merging pull requests. We’re reducing load on affected systems and monitoring the impact. We’ll share another update as we learn more.
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
We’ve mitigated the issue affecting pull request merges and Actions workflow start times by reducing load on affected systems. Pull Requests and Actions have recovered, and we’re continuing to monitor their performance.
On November 16, 2026, between 09:30 and 15:55 UTC, some pull request merges on GitHub timed out. On average, 2.9% of merge attempts timed out, with a peak of 7.1% at 15:17 UTC. Some GitHub Actions workflow runs triggered by pull requests were also delayed. Git operations such as push and fetch stayed available, with higher latency. This was a repeat of a shorter event on November 13, between 13:15 and 17:50 UTC, when 1.7% of merges timed out. Both events had the same cause: some of the storage servers that hold Git repository data reached their disk read bandwidth limits. A merge must be written to every copy of a repository, so one overloaded server slowed merges for every repository it hosts. Read load on these servers had been growing as part of a planned move of repositories to new infrastructure. A disk configuration setting on those servers also made them read far more data than…
CauseIn GitHub's words only
Some GitHub Actions workflow runs triggered by pull requests were also delayed.
GitHub has not published a post-mortem on its incident page.
Earlier at GitHub
Incident with Pull Requests
13 Nov 2026, major, open on the status page for 2 h 42 minImpact across multiple GitHub products including Actions, Pages, and Copilot products.
11 Nov 2026, critical, open on the status page for 33 minIncident with Git Operations and Pull Requests
10 Nov 2026, critical, open on the status page for 1 h 44 minDegraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot
9 Nov 2026, major, open on the status page for 49 min