Incidente di GitHub
Incident with Pull Requests
Risolto dopo 1 h 8 min.
- Inizio
- Fine
- Stato peggiore
- Prestazioni ridotte
- Sulla pagina di stato di GitHub
- Fonte
- Componenti
- Pull Requests
Cronologia
- Pagina di stato di GitHub · Reported Incident with Pull Requests
- Pagina di stato di GitHub · In analisi We are investigating reports of degraded performance for Pull Requests
- Pagina di stato di GitHub · In osservazione The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
- Pagina di stato di GitHub · In osservazione A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
- Pagina di stato di GitHub · Risolto 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…
Cita questo incidente
Site Qwality, “Incident with Pull Requests,” 20 set 2026, https://siteqwality.com/is-github-down/incidents/github-202609202213/
Puoi citarlo liberamente con un link a questa pagina.