GitHub incident
Incident with Pull Requests
Resolved after 1 h 8 min.
- Started
- Ended
- Worst state
- Degraded
- On GitHub’s status page
- Source
- Components
- Pull Requests
Timeline
- GitHub status page · Reported Incident with Pull Requests
- GitHub status page · Investigating We are investigating reports of degraded performance for Pull Requests
- GitHub status page · Monitoring The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
- GitHub status page · Monitoring A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
- GitHub status page · 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…
Cite this incident
Site Qwality, “Incident with Pull Requests,” Sep 20, 2026, https://siteqwality.com/is-github-down/incidents/github-202609202213/
Free to quote with a link to this page.