GitHub Actions Larger Runners VNet Injection Outage East US Region

What happened

GitHub Actions experienced significant delays affecting larger runners using VNet injection in the East US region from April 24 at 19:14 UTC through April 25 at 00:36 UTC. The incident was part of a broader multiservice impact affecting GitHub's infrastructure. GitHub resolved the issue after approximately 5 hours and 22 minutes of disruption. The company has committed to publishing a detailed root cause analysis once available.

Business impact

Teams using GitHub Actions for automated testing and deployment pipelines faced delayed or failed CI/CD workflows during the outage window. Organizations relying on larger runners for compute-intensive testing or deployment processes experienced significant delays in release cycles. Companies with time-sensitive deployment windows may have missed critical release deadlines.

Background

GitHub Actions larger runners provide enhanced compute resources for enterprise teams running complex build and test processes. VNet injection allows organizations to deploy these runners within their own virtual networks for enhanced security and compliance requirements. This capability is particularly critical for regulated industries that require network isolation for their CI/CD processes.

What this means for your team

Review your CI/CD pipeline dependencies and identify single points of failure in your GitHub Actions workflows. Implement fallback strategies such as self-hosted runners or alternative CI platforms for critical deployment windows. Document your runner configurations and VNet injection settings to quickly switch between deployment strategies during outages. Test your backup CI/CD processes regularly to ensure they can handle production workloads when needed.

What to watch

Monitor GitHub's status page for the promised root cause analysis, which may reveal systemic issues affecting larger runners. Watch for any follow-up incidents related to VNet injection or multiservice impacts that could indicate ongoing infrastructure instability.

Sources

Delayed Usage Data for Observability Events
Vercel Status
Turnstile Challenge Issues
Cloudflare Status
Increased errors on Image CDN
Netlify Status
Incident with Copilot
GitHub Status
Partial Observability Outage Affecting Compute Telemetry
Vercel Status
YUL (Montréal) on 2026-04-30
Cloudflare Status
Delays with Actions Jobs for Larger Runners using VNet Injection in the East US region
GitHub Status
Increased errors and latencies in Netlify UI
Netlify Status
Rendering issues for app.netlify.com
Netlify Status
Netlify App (app.netlify.com) Returning 404 Errors
Netlify Status

Timeline

4d ago now