GitHub Investigates Pull Request Merge Timeouts

GitHub is reporting an active service incident on its official status page.

Nov 16, 2026
•
5 min read
Technobezz
GitHub Investigates Pull Request Merge Timeouts

Don't Miss the Good Stuff

Get tech news that matters delivered to your inbox.

Updated 9:06 a.m. Eastern on November 16, 2026

GitHub says it continues to investigate elevated pull request merge timeouts, with mitigations so far failing to materially improve performance.

What is affected

Approximately 3% of pull request merges are timing out, compared with a baseline near 0.2%.

Official update timeline

, marked Investigating

We are investigating reports of degraded performance for Pull Requests

, marked Investigating

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.

, marked Investigating

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.

, marked Investigating

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.

, marked Investigating

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.

Read the official GitHub status page.

Track GitHub in the Technobezz status catalog.

Share