What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with GitHub now? Check the current statusAffected services
Updates (4)
- Sep 20, 2026, 11:22 PMIncident with Pull Requests
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 tha
GitHub ↗ - Sep 20, 2026, 10:32 PMIncident with Pull Requests
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
GitHub ↗ - Sep 20, 2026, 10:27 PMIncident with Pull Requests
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Sep 20, 2026, 10:13 PMIncident with Pull Requests
We are investigating reports of degraded performance for Pull Requests
GitHub ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow GitHub's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.