Actions delays in starting runs
Actions
Started:
Last official update:
Resolved:
Published incident duration: 38 minutes.
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 this period, events assigned to the affected component accumulated until an automatic reba
Read the full official incident ↗
MiniCrafts groups the provider's published notice by affected product. Unconfirmed scope stays unconfirmed. Published incident duration is not a measurement of downtime for every user.
What to do
Commit locally and push later; Actions jobs usually re-queue after recovery.
Check current product status and troubleshoot · Usage limits and reset rules
Official update timeline
- · resolved
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 this period, events assigned to the affected component accumulated until an automatic reba
- · monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- · investigating
Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.
- · investigating
We are investigating reports of degraded performance for Actions