# Actions runs are experiencing failures to start

- Provider: [GitHub Pages](https://down.guide/providers/github-pages)
- Confidence: Confirmed
- Impact: Partial outage
- lasted 22m
- started 2026-07-13 13:32 UTC
- Actions, Pages
- GitHub Pages states the impact was 2026-07-13 13:11 to 13:53 UTC (42m)
- id: DWN-ce75d805ed
- Official page: https://stspg.io/t0tfsmbt70w7

## Root cause
> The incident was triggered by a configuration change in an internal autoscaling component that contained outdated capacity threshold values.

Category: Deploy or config change. [Postmortem](https://stspg.io/t0tfsmbt70w7)

## Updates from GitHub Pages
### 2026-07-13 13:32 UTC: investigating
We are investigating reports of degraded availability for Actions

### 2026-07-13 13:32 UTC: investigating
Pages is experiencing degraded performance. We are continuing to investigate.

### 2026-07-13 13:39 UTC: monitoring
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

### 2026-07-13 13:53 UTC: resolved
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. 
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. 
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.

From the builder: does your app depend on GitHub Pages? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=github-pages) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention GitHub Pages.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-ce75d805ed), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.