Resolved after 1 hour 31 minutes, affecting us-east-1, on March 9, 2026.
All failover infrastructure is live and job service is restored. We will continue to address the underlying cause.
Affected components
Update timeline
- investigating Mar 09, 2026, 02:59 PM UTC
We are investigating reports of some GitHub runners failing to connect to GitHub
- identified Mar 09, 2026, 03:08 PM UTC
Errors seem to be caused in part by lack of instance capacity in our primary runner instance pool, we are activating a failover instance pool to unblock jobs.
- identified Mar 09, 2026, 03:20 PM UTC
Failover capacity is online and job throughput is increasing.
- identified Mar 09, 2026, 03:35 PM UTC
AWS are experiencing broad capacity constraints around our preferred instance type, we are activating a fallback to secondary instance type to address.
- monitoring Mar 09, 2026, 03:56 PM UTC
All failover infrastructure is live and job service is restored. We will continue to address the underlying cause.
- resolved Mar 09, 2026, 04:30 PM UTC
This incident has been resolved.
Your product runs on more than Depot
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services