Actions runs are experiencing failures to start

Summary

Actions runs are experiencing failures to start

On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of Actions jobs failed to start and 2% were delayed more than 5 minutes. <br /><br />The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values. This caused a critical Actions service to scale below its required baseline, reducing capacity for workflow processing. We identified the regression, rolled back the change, and restored service capacity. New workflow executions recovered by 13:39 UTC. Full recovery was reached by 13:53 UTC after the queued backlog was drained. <br /><br />To prevent recurrence, we have added deployment guardrails to validate that autoscaling inputs are current and to detect drift between planned and live scaling state before autoscaling changes are applied.

• Started

  Jul 13, 2026 · 1:32 PM

• Resolved

  Jul 13, 2026 · 1:53 PM

• Duration

  21m

• Severity

  Major

• ◐

  Investigating

  Jul 13 · 1:32 PM GitHub

  We are investigating reports of degraded availability for Actions

• ◐

  Investigating

  Jul 13 · 1:32 PM GitHub

  Pages is experiencing degraded performance. We are continuing to investigate.

• ◉

  Monitoring

  Jul 13 · 1:39 PM GitHub

  The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

• ✓

  Resolved

  Jul 13 · 1:53 PM GitHub

  On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of Actions jobs failed to start and 2% were delayed more than 5 minutes. <br /><br />The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values. This caused a critical Actions service to scale below its required baseline, reducing capacity for workflow processing. We identified the regression, rolled back the change, and restored service capacity. New workflow executions recovered by 13:39 UTC. Full recovery was reached by 13:53 UTC after the queued backlog was drained. <br /><br />To prevent recurrence, we have added deployment guardrails to validate that autoscaling inputs are current and to detect drift between planned and live scaling state before autoscaling changes are applied.