‹ Back to incident history

Incident with Pull Requests

ResolvedMinor incidentGitHub
Monday, September 21, 2026 06:13 – Monday, September 21, 2026 07:22 (1 hr 8 min)
Affected components
Pull Requests
Updates
ResolvedMonday, September 21, 2026 07:22

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.

MonitoringMonday, September 21, 2026 06:32

A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.

MonitoringMonday, September 21, 2026 06:27

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

InvestigatingMonday, September 21, 2026 06:13

We are investigating reports of degraded performance for Pull Requests

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview