- Level
- confirmed
- Worst impact
- Major outage
- Components
- Actions, Pages
- Down Index
- 62of 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 3h 38m it lasted.
Anything that failed between 2026-10-05 19:11 UTC and 2026-10-05 22:49 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.
Root cause
The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services.
Category: Data center or power
Read the postmortemUpdates from GitHub Pages 12
- investigating
We are investigating reports of degraded performance for Actions
provider
- investigating
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
provider
- investigating
We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
provider
- investigating
We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
provider
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
provider
- investigating
In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
provider
- investigating
Pages is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
provider
- investigating
We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
provider
- investigating
Actions is operating normally.
provider
- investigating
Pages is operating normally.
provider
- resolved
On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services. We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC. We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for 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-10b868a96a
Is GitHub Pages still down?
No, this incident was resolved 2026-10-05 22:49 UTC. For GitHub Pages's live state, see https://down.guide/github-pages.
How long did it last?
3h 38m, from 2026-10-05 19:11 UTC to 2026-10-05 22:49 UTC, by the times GitHub Pages posted.
What was affected?
GitHub Pages named Actions, Pages.
What caused it?
Data center or power. GitHub Pages wrote: "The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services." The postmortem: https://stspg.io/c11dc9nb1zdq
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.