Resolved
GitHub · degraded service
Incident with Pull Requests
Posted 20 Sep 22:13 UTC, last seen today 11:33 UTC.
What it affected
As the provider names itWhat the provider posted
Newest first- 20 Sep 23:22 UTCResolvedOn 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.
- 20 Sep 22:32 UTCUpdateA git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
- 20 Sep 22:27 UTCMonitoringThe degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
- 20 Sep 22:13 UTCInvestigatingWe are investigating reports of degraded performance for Pull Requests
Around it
From the sources ChangeIntel reads; a match in time is not a causeElsewhere at the same time
- Cloudflare Hyperdrive Degraded Performance
Earlier incidents in the 14 days before
- GitHub: Elevated rate of errors for OpenAI models provided by CopilotService incident · 17 Sep
- GitHub: Degradation with Gemini 3.8 FlashService incident · 16 Sep
- GitHub: Disruption with some GitHub servicesService incident · 2 times, latest 15 Sep
- GitHub: Actions Larger Runner Jobs for some customers may be slow to startService incident · 14 Sep
- GitHub: Incident with several GitHub ServicesService incident · 13 Sep
What changed
First observed 14 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.
Keep track
- Service status now: every provider ChangeIntel reads, with ongoing incidents first.
- Status RSS feed: new and ended incidents as they happen.
- Everything about GitHub: its changes, known issues and incidents on one timeline.