Incident with Actions: Queue Run Failures


Incident resolved in 1h10m38s

Resolved

On March 18th, 2025, between 23:20 UTC and March 19th, 2025 00:15 UTC, the Actions service experienced degradation, leading to run start delays. During the incident, about 0.3% of all workflow runs queued during the time failed to start, about 0.67% of all workflow runs were delayed by an average of 10 minutes, and about 0.16% of all workflow runs ultimately ended with an infrastructure failure. This was due to a networking issue with an underlying service provider. At 00:15 UTC the service provider mitigated their issue, and service was restored immediately for Actions. We are working to improve our resilience to downtime in this service provider to reduce the time to mitigate in any future recurrences.

1742345747

Investigating

Actions is operating normally.

1742345740

Investigating

The provider has reported full mitigation of the underlying issue, and Actions has been healthy since approximately 00:15 UTC.

1742345711

Investigating

We are continuing to investigate issues with delayed or failed workflow runs with Actions. We are engaged with a third-party provider who is also investigating issues and has confirmed we are impacted.

1742343768

Investigating

Some customers may be experiencing delays or failures when queueing workflow runs

1742341552

Investigating

We are investigating reports of degraded performance for Actions

1742341509