Incident with Actions

Resolved

On June 4, 2025, between 14:35 UTC and 15:50 UTC , the Actions service experienced degradation, leading to run start delays. During the incident, about 15.4% of all workflow runs were delayed by an average of 16 minutes. An unexpected load pattern revealed a scaling issue in our backend infrastructure. We mitigated the incident by blocking the requests that triggered this pattern. We are improving our rate limiting mechanisms to better handle unexpected load patterns while maintaining service availability. We are also strengthening our incident response procedures to reduce the time to mitigate for similar issues in the future.

Investigating

We have applied mitigations and are monitoring for recovery.

Investigating

We are currently investigating delays with Actions triggering for some users.

Investigating

We are investigating reports of degraded performance for Actions