Incident with Actions and 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
- 26 Aug 2026, 22:56:31 UTC
- Anbieterdatensatz aktualisiert
- 28 Aug 2026, 22:10:28 UTC
- Ausdrücklicher Anbieterbeginn
- 26 Aug 2026, 22:56:31 UTC
- Ausdrückliches Anbieterende
- 27 Aug 2026, 00:26:44 UTC
Vom Anbieter gemeldete betroffene Komponenten
- Actions
br0l2tvcx85d - 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 August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. <br /><br />Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. <br /><br />We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. <br /><br />We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - monitoring
The degradation affecting Actions and 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 confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC - investigating
We are investigating reports of degraded performance for Actions and Pull Requests
In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC