Incidente di GitHub
Delays in commit processing
Risolto dopo 1 h.
- Inizio
- Fine
- Stato peggiore
- Prestazioni ridotte
- Sulla pagina di stato di GitHub
- Fonte
- Componenti
- Pull Requests
Cronologia
- Pagina di stato di GitHub · Reported Delays in commit processing
- Pagina di stato di GitHub · In analisi We are investigating reports of degraded performance for Pull Requests
- Pagina di stato di GitHub · In analisi Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
- Pagina di stato di GitHub · In analisi Time to update pull request diffs have improved to normal thresholds.
- Pagina di stato di GitHub · Risolto 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…
Cita questo incidente
Site Qwality, “Delays in commit processing,” 1 set 2026, https://siteqwality.com/is-github-down/incidents/github-202609011500/
Puoi citarlo liberamente con un link a questa pagina.