Actions runs are experiencing failures to start

What to do

• Check whether you use GitHub Actions, Pages. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 22m it lasted.

  Anything that failed between 2026-07-13 13:32 UTC and 2026-07-13 13:53 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 4

1. investigatingJul 13, 2026, 1:32 PM UTC

   We are investigating reports of degraded availability for Actions

   provider

2. investigatingJul 13, 2026, 1:32 PM UTC

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

   provider

3. monitoringJul 13, 2026, 1:39 PM UTC

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

   provider

4. resolvedJul 13, 2026, 1:53 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.