ARCHIVIERTER OFFIZIELLER INCIDENT

Actions Job Delays

GitHub · Letzter gespeicherter Anbieterstatus: resolved

Aktueller Dienstbericht →

Offizielle Quellentexte werden in Originalsprache angezeigt.

Historische Belege.

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
01 Oct 2026, 14:47:48 UTC
Anbieterdatensatz aktualisiert
01 Oct 2026, 17:56:54 UTC
Ausdrücklicher Anbieterbeginn
01 Oct 2026, 14:47:48 UTC
Ausdrückliches Anbieterende
01 Oct 2026, 17:56:54 UTC

Vom Anbieter gemeldete betroffene Komponenten

  • Actions br0l2tvcx85d

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.

  1. resolved

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  2. investigating

    GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  3. investigating

    We are currently applying a mitigation and anticipate recovery within thirty minutes.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  4. investigating

    We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  5. investigating

    We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  6. investigating

    Actions is experiencing degraded performance. We are continuing to investigate.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  7. monitoring

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  8. investigating

    Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  9. investigating

    We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
  10. investigating

    We are investigating reports of degraded performance for Actions

    In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC