Actions delays in starting runs

Cronologia

1. 13:56 UTC Pagina di stato di GitHub · Reported Actions delays in starting runs
2. 13:56 UTC Pagina di stato di GitHub · In analisi We are investigating reports of degraded performance for Actions
3. 14:22 UTC Pagina di stato di GitHub · In analisi Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.
4. 14:26 UTC Pagina di stato di GitHub · In osservazione The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
5. 14:34 UTC Pagina di stato di GitHub · Risolto On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewhere. During…