Companies / GitHub / incidents
GitHub: Incident with Actions
GitHub reported critical Actions and Pages degradation starting 2026-10-05 19:11 UTC, resolved at 2026-10-05 22:49 UTC (3 h 37 min). Runner delays meant 26.5% of GitHub-hosted jobs did not start within five minutes, delaying customer workflows. GitHub applied mitigations, cleared queued jobs, and reported both services operating normally.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: ActionsPages
Discussed on Hacker News
- 103 points · 64 comments · posted · posted 57 min after the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Timeline of updates
- investigating
We are investigating reports of degraded performance for Actions
- 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.
- 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.
- 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.
- investigating
Actions is experiencing degraded availability. We are continuing to investigate.
- 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.
- investigating
Pages is experiencing degraded performance. We are continuing to investigate.
- investigating
Actions is experiencing degraded performance. We are continuing to investigate.
- 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.
- investigating
Actions is operating normally.
- investigating
Pages is operating normally.
- 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. <br /><br /> <br />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. <br /><br /><br />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. <br /><br /><br />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. <br /><br /> <br />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.
Rewindex changes for this incident
- Critical incident: Incident with Actions 2026-10-05 19:11 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). GitHub profile · Recent GitHub incidents · Markdown · JSON