Affected components
Update timeline
- investigating Mar 09, 2026, 02:59 PM UTC
Status: Investigating We are investigating reports of some GitHub runners failing to connect to GitHub Affected components us-east-1 (Partial outage)
- identified Mar 09, 2026, 03:08 PM UTC
Status: Identified 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. Affected components us-east-1 (Partial outage)
- identified Mar 09, 2026, 03:20 PM UTC
Status: Identified Failover capacity is online and job throughput is increasing. Affected components us-east-1 (Degraded performance)
- identified Mar 09, 2026, 03:35 PM UTC
Status: Identified AWS are experiencing broad capacity constraints around our preferred instance type, we are activating a fallback to secondary instance type to address. Affected components us-east-1 (Degraded performance)
- monitoring Mar 09, 2026, 03:56 PM UTC
Status: Monitoring All failover infrastructure is live and job service is restored. We will continue to address the underlying cause. Affected components us-east-1 (Degraded performance)
- resolved Mar 09, 2026, 04:30 PM UTC
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Looking to track Depot downtime and outages?
Pingoru polls Depot's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Depot reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Depot alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required