GitHub incident
Delays in commit processing
Resolved after 1 h.
- Started
- Ended
- Worst state
- Degraded
- On GitHub’s status page
- Source
- Components
- Pull Requests
Timeline
- GitHub status page · Reported Delays in commit processing
- GitHub status page · Investigating We are investigating reports of degraded performance for Pull Requests
- GitHub status page · Investigating Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
- GitHub status page · Investigating Time to update pull request diffs have improved to normal thresholds.
- GitHub status page · Resolved On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than 140,000 customer accounts had at least one delayed refresh during the most affected 75 minutes. Pushing commits and opening pull requests continued to work normally. The incident was caused by a sharp, concentrated surge in push volume that saturated worker pools and job queueing infrastructure. Autoscaling did not…
Cite this incident
Site Qwality, “Delays in commit processing,” Sep 1, 2026, https://siteqwality.com/is-github-down/incidents/github-202609011500/
Free to quote with a link to this page.