GitHub Copilot · 85d ago
Actions runs are experiencing failures to start
ResolvedYes — GitHub Copilot had a problem on July 13, 2026, and GitHub Copilot has since marked it resolved. GitHub Copilot's latest word: “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.”
Timeline
Started: 7/13/2026, 1:32:22 PM
Last update: 7/15/2026, 6:24:55 PM
Resolved: 7/13/2026, 1:53:57 PM
Affected: br0l2tvcx85d, vg70hn9s2tyj
Updates
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. <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.
7/13/2026, 1:53:57 PM
monitoring
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
7/13/2026, 1:39:27 PM
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
7/13/2026, 1:32:44 PM
investigating
We are investigating reports of degraded availability for Actions
7/13/2026, 1:32:22 PM
More GitHub Copilot incidents
- Incident with Git Operations, Issues, Actions and Pull Requests — resolved, 20h ago
- Incident with Git Operations, Pull Requests and Actions — resolved, 22h ago
- Several services are degraded — resolved, 2d ago
- Incident with Actions — resolved, 3d ago
- Disruption with some GitHub services — resolved, 3d ago
- Elevated request latency — resolved, 7d ago