Sep 20, 23:22 UTC
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. 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. Sep 20, 22:32 UTC
Update - A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery. Sep 20, 22:27 UTC
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability. Sep 20, 22:13 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
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.
Posted Sep 20, 2026 - 23:22 UTC
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
Posted Sep 20, 2026 - 22:32 UTC
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Posted Sep 20, 2026 - 22:27 UTC
We are investigating reports of degraded performance for Pull Requests
Posted Sep 20, 2026 - 22:13 UTC
This incident affected: Pull Requests.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Incident with Actions and Pull Requests | 0 | 14.09 | 27-08-2026 |
| 2 | Delays in commit processing | 0 | 14.66 | 01-09-2026 |
| 3 | Degradation in repos contents API | 0 | 12.8 | 04-09-2026 |
| 4 | Incident with several GitHub Services | 0 | 15.23 | 13-09-2026 |
| 5 | Disruption with some GitHub services | 0 | 10.97 | 15-09-2026 |
| 6 | Copilot Code Review is unable to complete reviews | 0 | 9.01 | 28-09-2026 |
| 7 | Incident across several services | 0 | 13.85 | 24-09-2026 |
| 8 | Incident with Actions | 0 | 12.14 | 26-08-2026 |
| 9 | Incident with Actions | 0 | 8 | 05-10-2026 |
| 10 | Elevated request latency | 0 | 14.4 | 01-10-2026 |