GitHub Copilot · 15d ago
Incident with Pull Requests
ResolvedYes — GitHub Copilot had a problem on September 20, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “On September 20, 2026, between 21:46 and 22:24 UTC the Pull Requests service was degraded and pull request merge and test-merge commits were created late, with delays reaching approximately four minutes at peak. Merge commits were delayed rather than lost. Because some Actions workflow runs start only after a pull request's merge commit is created, a subset of workflow runs for pull request events were also delayed. <br /><br />This was due to a routine repository maintenance job for an unusually large repository consuming nearly all of the memory on a single Git storage server, which left that server unable to serve the Git operations used to create merge commits. <br /><br />We mitigated the incident by removing the affected server from service at 22:18 UTC, after which the queued merge commits were created within six minutes. <br /><br />We have capped the memory a single repository maintenance job may consume so that one repository cannot exhaust a server, and we have improved monitoring and alerting on storage server health to reduce our time to detection and mitigation of issues like this one in the future.”
Timeline
Started: 9/20/2026, 10:13:37 PM
Last update: 9/24/2026, 9:29:12 PM
Resolved: 9/20/2026, 11:22:16 PM
Affected: hhtssxt0f5v2
Updates
resolved
On September 20, 2026, between 21:46 and 22:24 UTC the Pull Requests service was degraded and pull request merge and test-merge commits were created late, with delays reaching approximately four minutes at peak. Merge commits were delayed rather than lost. Because some Actions workflow runs start only after a pull request's merge commit is created, a subset of workflow runs for pull request events were also delayed. <br /><br />This was due to a routine repository maintenance job for an unusually large repository consuming nearly all of the memory on a single Git storage server, which left that server unable to serve the Git operations used to create merge commits. <br /><br />We mitigated the incident by removing the affected server from service at 22:18 UTC, after which the queued merge commits were created within six minutes. <br /><br />We have capped the memory a single repository maintenance job may consume so that one repository cannot exhaust a server, and we have improved monitoring and alerting on storage server health to reduce our time to detection and mitigation of issues like this one in the future.
9/20/2026, 11:22:16 PM
monitoring
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
9/20/2026, 10:32:02 PM
monitoring
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
9/20/2026, 10:27:28 PM
investigating
We are investigating reports of degraded performance for Pull Requests
9/20/2026, 10:13:37 PM
More GitHub Copilot incidents
- Actions Job Delays — resolved, 9d ago
- Disruption with some GitHub services — resolved, 4d ago
- Incident with Git Operations, Issues, Actions and Pull Requests — resolved, 2d ago
- Incident with Git Operations, Pull Requests and Actions — resolved, 3d ago
- Several services are degraded — resolved, 3d ago
- Incident with Actions — resolved, 4d ago