- Level
- confirmed
- Worst impact
- Major outage
- Components
- Actions, Pages
- Down Index
- 64of 100
What to do
Check whether you use GitHub Pages 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 9h 18m it lasted.
Anything that failed between 2026-07-09 04:34 UTC and 2026-07-09 13:52 UTC may need a replay.Subscribe to GitHub Pages's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=github-pages works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from GitHub Pages 14
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
Approximately 5% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.
provider
- investigating
We are continuing to work on a mitigation.
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start.
provider
- investigating
Approximately 30% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A smaller percentage of those are exhausting retries and failing to start. This has caused some customers to exceed their hosted compute concurrency and experience increased impact. We are continuing to working on infrastructure mitigations. Next update in one hour.
provider
- investigating
Pages is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
We're seeing Actions and Pages recovery. For a period of approximate 20 minutes ~96% of GitHub Actions runs on GitHub-hosted runners were failing to start, but has now recovered and we are seeing jobs processing. GitHub pages builds were also failing during that period, but Pages are still accessible. We are continuing to monitor for full recovery.
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
We are continuing to monitor slow recovery in Actions and Pages builds as the system works through the high volume of backlog. Customers may see a small rate of API and job failures as the system is recovering. Copilot Cloud Agent and Copilot Code Review also failed to start for approximately 30 minutes during this incident, and we are monitoring recovery. Pages were accessible throughout the incident.
provider
- monitoring
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
provider
- monitoring
Actions, Pages builds, Copilot Cloud Agent, and Copilot Code review have all recovered and are mitigated. We are continuing to monitor to ensure full recovery, and investigating the health of the affected infrastructure.
provider
- resolved
On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 8% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 2% failed to start. At 13:39 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.
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-8fa69212bb
Is GitHub Pages still down?
No, this incident was resolved 2026-07-09 13:52 UTC. For GitHub Pages's live state, see https://down.guide/github-pages.
How long did it last?
9h 18m, from 2026-07-09 04:34 UTC to 2026-07-09 13:52 UTC, by the times GitHub Pages posted.
What was affected?
GitHub Pages named Actions, Pages.
What caused it?
GitHub Pages hasn't published a root cause. If it does, it shows here.
Where does this come from?
GitHub Pages's official status page, https://www.githubstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.