GitHub Actions suffered elevated queue times and failures on Standard Hosted Runners in East US on May 5, affecting up to 10% of runs.
Key Takeaways
Incident began at 13:37 UTC; root cause traced to compute capacity issues with GitHub’s underlying cloud provider in East US.
Peak impact: 10% of Actions runs seeing failures or elevated queue times on Standard Hosted Runners.
Hosted Runners with Private Networking in East US remained affected longer; mitigation was applied by 15:54 UTC.
Workaround available during incident: Hosted Runners with private networking could fail over to a different Azure region.
Hacker News Comment Review
Commenters linked the capacity strain to explosive GitHub Actions growth: GitHub’s COO noted Actions grew from 500M minutes/week, with commits now tracking 14 billion/year, driven heavily by agentic workflows.
There is debate over whether GitHub’s status reporting is honest – the official status page showed 100% uptime for April despite recurring incidents, raising questions about how downtime is classified.
Several commenters called for pricing intervention – raising Actions prices or returning to paid-tier gating – to throttle agent-driven demand overwhelming shared infrastructure.
Notable Comments
@jameson: Asks whether GitHub publishes post-mortems and flags that spiking incident frequency signals a systemic, not one-off, problem.
