Incident with Pull Requests
GitHub · Letzter gespeicherter Anbieterstatus: resolved
Offizielle Quellentexte werden in Originalsprache angezeigt.
Letzter Ereignisstatus ist nicht aktueller Dienststatus. Quellen können unvollständig sein; Verschwinden bestätigt keine Erholung. Für neuere Belege aktuellen Bericht/Quelle öffnen.
Gespeicherte Ereignisdetails
- Anbieterstatus
- resolved
- Anbieterauswirkungen
- minor
- Anbieterdatensatz erstellt
- 20 Sep 2026, 22:13:37 UTC
- Anbieterdatensatz aktualisiert
- 24 Sep 2026, 21:29:12 UTC
- Ausdrücklicher Anbieterbeginn
- 20 Sep 2026, 22:13:37 UTC
- Ausdrückliches Anbieterende
- 20 Sep 2026, 23:22:16 UTC
Vom Anbieter gemeldete betroffene Komponenten
- Pull Requests
hhtssxt0f5v2
Zuordnungen beschreiben gemeldeten Ereignisumfang, keine aktuelle Komponentenverfügbarkeit oder verifizierten Abhängigkeiten.
Die Erstellung eines Datensatzes ist nicht zwingend der Ausfallbeginn. Nicht gemeldete Zeiten bleiben unbekannt. Aus Erfassungszeiten berechnen wir keine Ausfalldauer.
Anbieterupdates in gespeicherten Revisionen
Neueste zuerst. Bis zu 100 verschiedene Updates aus den letzten 20 gespeicherten Revisionen. Geänderte Formulierungen bei gleicher Anbieterzeit bleiben separat.
- 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. <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 that server unable to serve the Git operations used to create merge commits. <br /><br />We mitigated the incident by removing the affected server from service at 22:18 UTC, after which the queued merge commits were created within six minutes. <br /><br />We have capped the memory a single repository maintenance job may consume so that one repository cannot exhaust a server, and we have improved monitoring and alerting on storage server health to reduce our time to detection and mitigation of issues like this one in the future.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - monitoring
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for Pull Requests
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC