GitHub outage on September 20, 2026: Incident with Pull Requests

GitHub reported an incident affecting GitHub for 1 hour 9 minutes on 20 September 2026, from 22:13 to 23:22 UTC.

github.com All times UTC

Resolved

Official incident reported by GitHub

Started: 22:13; 20 Sep 2026 UTC
Resolved: 23:22; 20 Sep 2026 UTC
Duration: 1h 9m; 1 hour 9 minutes
Impact: Minor; as rated by GitHub
Updates: 4; posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Incident with Pull Requests

Resolved Minor impact 20 Sep 2026 22:13 UTC View on GitHub's status page

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

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

All GitHub incidents Live GitHub status Every service we track

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.