Incident with Pull Requests
Final update
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. 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. 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. 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
- Resolved · Sep 20, 23:22 UTC
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. 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. 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. 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.
- Monitoring · Sep 20, 22:32 UTC
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
- Monitoring · Sep 20, 22:27 UTC
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
- Investigating · Sep 20, 22:13 UTC
We are investigating reports of degraded performance for Pull Requests
More from GitHub
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2416:51 UTC | Disruption with billing information updates | minor | 3h 50m |
| Sep 2310:11 UTC | Incident across several services | minor | 18h 44m |
| Sep 1720:59 UTC | Elevated rate of errors for OpenAI models provided by Copilot | minor | 50m |
| Sep 1607:20 UTC | Degradation with Gemini 3.8 Flash | major | 10h 28m |
| Sep 1519:11 UTC | Disruption with some GitHub services | minor | 49m |
| Sep 1509:47 UTC | Disruption with some GitHub services | minor | 1h 30m |
Also caused by storage
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1715:50 UTC | AutoOps node metrics temporarily unavailable in some regions | major | 41m | |
| Sep 1015:26 UTC | Unresponsive Projects | major | 27h 40m | |
| Jul 1909:51 UTC | Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1 | minor | 5h 41m | |
| Mar 720:07 UTC | Outage for prod-eu-central-0 due to AWS S3 outage. | none | 36h 52m | |
| Mar 719:53 UTC | Increased Error Rates | major | 1h 11m | |
| Nov 2808:28 UTC | Delayed Logs in EU Region | minor | 10h 46m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.