Incident with Actions

Gespeicherte Ereignisdetails

Anbieterstatus

resolved

Anbieterauswirkungen

major

Anbieterdatensatz erstellt

29 Jul 2026, 15:26:24 UTC

Anbieterdatensatz aktualisiert

30 Jul 2026, 01:28:07 UTC

Ausdrücklicher Anbieterbeginn

29 Jul 2026, 15:26:24 UTC

Ausdrückliches Anbieterende

29 Jul 2026, 16:00: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. resolved29 Jul 2026, 16:00:54 UTC

   On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts. <br /><br />The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future.

   In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
2. monitoring29 Jul 2026, 15:40:35 UTC

   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
3. investigating29 Jul 2026, 15:34:07 UTC

   We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure.

   In gespeicherter Revision gesehen um 06 Oct 2026, 13:58:39 UTC
4. investigating29 Jul 2026, 15:26:24 UTC

   We are investigating reports of degraded availability for Actions

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