Skip to main content
GitHub Actions

Actions runs are experiencing failures to start

Partial outage Lasted 22m · started · GitHub Actions's page

Level
confirmed
Worst impact
Partial outage
Components
Actions, Pages
Down Index
45of 100

What to do

  • Check whether you use GitHub Actions 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 Actions's feed to hear about the next one first. RSS feed

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

Updates from GitHub Actions 4

  1. investigating

    We are investigating reports of degraded availability for Actions

    provider

  2. investigating

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

    provider

  3. monitoring

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

    provider

  4. 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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-125ea30221

Is GitHub Actions still down?

No, this incident was resolved 2026-07-13 13:53 UTC. For GitHub Actions's live state, see https://down.guide/github-actions.

How long did it last?

22m, from 2026-07-13 13:32 UTC to 2026-07-13 13:53 UTC, by the times GitHub Actions posted.

What was affected?

GitHub Actions named Actions, Pages.

What caused it?

GitHub Actions hasn't published a root cause. If it does, it shows here.

Where does this come from?

GitHub Actions's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.