Skip to content
GitHub · Developer toolsSep 20, 2026, 22:13 UTC

Incident with Pull Requests

MinorStorageUpdated 6h ago
Sep 20, 22:13 UTCSep 20, 23:22 UTC
Duration
1h 9m
Impact
Minor
Root cause
Storage
GitHub, 90 days
69 incidents
Affected
Pull Requests
Status page

Final update

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.

Timeline

  1. Resolved · Sep 20, 23:22 UTC
    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.
  2. Monitoring · Sep 20, 22:32 UTC
    A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
  3. Monitoring · Sep 20, 22:27 UTC
    The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
  4. Investigating · Sep 20, 22:13 UTC
    We are investigating reports of degraded performance for Pull Requests

More from GitHub

Full history
StartedIncidentDuration
Sep 2416:51 UTCDisruption with billing information updates3h 50m
Sep 2310:11 UTCIncident across several services18h 44m
Sep 1720:59 UTCElevated rate of errors for OpenAI models provided by Copilot50m
Sep 1607:20 UTCDegradation with Gemini 3.8 Flash10h 28m
Sep 1519:11 UTCDisruption with some GitHub services49m
Sep 1509:47 UTCDisruption with some GitHub services1h 30m

Also caused by storage

All
StartedIncidentDuration
Sep 1715:50 UTCAutoOps node metrics temporarily unavailable in some regionsElastic41m
Sep 1015:26 UTCUnresponsive ProjectsSupabase27h 40m
Jul 1909:51 UTCBlock Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1DigitalOcean5h 41m
Mar 720:07 UTCOutage for prod-eu-central-0 due to AWS S3 outage.Grafana Labs36h 52m
Mar 719:53 UTCIncreased Error RatesAWS1h 11m
Nov 2808:28 UTCDelayed Logs in EU RegionMailgun10h 46m

Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Outages by email

Saturday mornings: the week's major outages, new postmortems and disclosed breaches, only in weeks that had some.

Double opt-in. Unsubscribe any time.