Вход на сайт

Просмотр новости

Найдите то, что Вас интересует

Incident with Pull Requests

Дата публикации: 20-09-2026 23:22:16


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

Основное содержимое страницы с новостью.

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.

Posted Sep 20, 2026 - 23:22 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.

Posted Sep 20, 2026 - 22:32 UTC

Monitoring

The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Posted Sep 20, 2026 - 22:27 UTC

Investigating

We are investigating reports of degraded performance for Pull Requests

Posted Sep 20, 2026 - 22:13 UTC

This incident affected: Pull Requests.

Схожие новости

#Наименование новостиТональностьИнформативностьДата публикации
1Incident with Actions and Pull Requests014.0927-08-2026
2Delays in commit processing014.6601-09-2026
3Degradation in repos contents API012.804-09-2026
4Incident with several GitHub Services015.2313-09-2026
5Disruption with some GitHub services010.9715-09-2026
6Copilot Code Review is unable to complete reviews09.0128-09-2026
7Incident across several services013.8524-09-2026
8Incident with Actions012.1426-08-2026
9Incident with Actions0805-10-2026
10Elevated request latency014.401-10-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 10.44. Источник: www.githubstatus.com.