Incident with Pull Requests
GitHub · Last saved provider status: resolved
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- resolved
- Provider impact
- minor
- Provider record created
- 20 Sep 2026, 22:13:37 UTC
- Provider record updated
- 24 Sep 2026, 21:29:12 UTC
- Explicit provider start
- 20 Sep 2026, 22:13:37 UTC
- Explicit provider end
- 20 Sep 2026, 23:22:16 UTC
Affected components reported by the provider
- Pull Requests
hhtssxt0f5v2
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- 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.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - monitoring
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for Pull Requests
Seen in a saved revision at 06 Oct 2026, 13:58:39 UTC