Depot had 35 outages in the last 2 years — averaging 1.4 incidents per month.
There were 35 Depot outages since December 10, 2025. Each is summarised below — incident details, duration, and resolution information.
Status: Investigating We are investigating increased queue times for GitHub Actions jobs Affected components us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved, all jobs are processing normally. Affected components us-east-1 (Operational)
Status: Investigating We are receiving reports of GitHub Actions runners disconnecting from GitHub's control plane. We are investigating. Affected components GitHub.com (Partial outage)
Status: Monitoring We have deployed a mitigation for the disconnect and are monitoring Affected components GitHub.com (Operational)
Status: Resolved This incident is resolved Affected components GitHub.com (Operational)
Status: Investigating GitHub jobs using Depot managed are unable to start. Affected components us-east-1 (Partial outage)
Status: Monitoring We've applied a fix and are monitoring Affected components us-east-1 (Operational)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Identified Depot CI jobs not syncing checks to GitHub. Affected components Depot CI (Degraded performance)
Status: Monitoring We've applied a fix and are monitoring. Affected components Depot CI (Operational)
Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)
Status: Investigating We are seeing high queue times and are scaling up. Affected components Depot CI (Degraded performance)
Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)
Status: Identified We are deploying a fix for an issue causing delays starting GitHub Actions runners in us-east-1 Affected components us-east-1 (Partial outage)
Status: Identified Fix is deployed, we are processing the backlog of jobs now Affected components us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Identified We are seeing some customers with very slow I/O at the moment and are starting to mitigate. Affected components us-east-1 (Degraded performance)
Status: Monitoring We are seeing recovery now and new builds are having normal disk i/o. Affected components us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Investigating We are investigating an issue preventing some Depot CI jobs from starting. Affected components Depot CI (Partial outage)
Status: Monitoring We have deployed a fix and jobs are processing. We are continuing to monitor. Affected components Depot CI (Operational)
Status: Identified We are still seeing some intermittent failures and are investigating. Affected components Depot CI (Partial outage)
Status: Monitoring Jobs are processing again, we are continuing to monitor. Affected components Depot CI (Operational)
Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)
Status: Investigating Investigating the failure of some Depot CI jobs being able to start. Affected components Depot CI (Partial outage)
Status: Monitoring We identified the issue as upstream rate limits. We are monitoring to make sure the issue has cleared. Affected components Depot CI (Operational)
Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)
Status: Identified Job's relying on OIDC are unable to be authenticated. The issue has been identified and we're deploying a fix. Affected components Depot CI (Partial outage)
Status: Resolved This has been resolved. Affected components Depot CI (Operational)
Status: Investigating We are investigating higher queue times for Depot CI jobs. Affected components Depot CI (Degraded performance)
Status: Monitoring We've deployed a fix and are monitoring recovery. Affected components Depot CI (Operational)
Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)
Status: Investigating GitHub is currently experiencing an outage: https://www.githubstatus.com/incidents/72q3n8yxthcy that is affecting a number of internal services. We expect this to disrupt delivery of jobs to Depot-hosted runners. We'll continue to monitor the situation. Affected components GitHub.com (Partial outage)
Status: Monitoring GitHub has indicated that their incident has been mitigated. We'll continue to monitor the situation. Affected components GitHub.com (Operational)
Status: Resolved This incident has been resolved. Affected components GitHub.com (Operational)
Status: Investigating Jobs are still running. We are investigating the missing logs and metrics. Affected components Depot CI (Degraded performance) us-east-1 (Degraded performance)
Status: Identified Identified the issue and working on a fix. Affected components us-east-1 (Degraded performance) Depot CI (Operational)
Status: Investigating We are investigating. Affected components us-east-1 (Degraded performance) Depot CI (Degraded performance)
Status: Monitoring We've applied a fix and are monitoring. Affected components us-east-1 (Operational) Depot CI (Operational)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational) Depot CI (Operational)
Status: Investigating Investigating Affected components us-east-1 (Full outage) eu-central-1 (Full outage) API (Full outage) Depot Cache (Full outage) Container Registry (Full outage) Depot CI (Full outage) us-east-1 (Full outage) Dashboard (Full outage)
Status: Identified We have identified the cause as an outage of our primary database Affected components eu-central-1 (Full outage) API (Full outage) Depot Cache (Full outage) Container Registry (Full outage) Depot CI (Full outage) us-east-1 (Full outage) Dashboard (Full outage) us-east-1 (Full outage)
Status: Identified We have worked with our database provider to restore database connectivity - CI jobs and container builds are operational and are now processing the backlog of jobs. Affected components eu-central-1 (Degraded performance) API (Operational) Depot Cache (Degraded performance) Container Registry (Degraded performance) Depot CI (Degraded performance) us-east-1 (Degraded performance) Dashboard (Operational) us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved, the backlog of jobs has processed successfully. Affected components us-east-1 (Operational) Dashboard (Operational) us-east-1 (Operational) eu-central-1 (Operational) API (Operational) Depot Cache (Operational) Container Registry (Operational) Depot CI (Operational)
Status: Investigating We're investigating the reports of early sandbox termination. We are seeing some jobs work but many fail. Affected components Depot CI (Partial outage)
Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)
Status: Investigating We are investigating reports of increased queue time for x86 Ubuntu GitHub Actions jobs. Affected components us-east-1 (Degraded performance)
Status: Identified We are continuing to see capacity issues across us-east-1 and us-east-2 inside of AWS. While this is ongoing, we are rerouting jobs to AZs in regions with capacity. We are in contact with AWS to get additional capacity in the impacted regions released. This degraded performance is only impacting GitHub Actions runners to date. Affected components us-east-1 (Degraded performance)
Status: Monitoring We have deployed an additional remediation for our cross-region failover to increase job-launch throughput while AWS instance capacity is limited. Early signs are showing fewer capacity errors, but we are continuing to monitor the situation. Affected components us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Identified We have identified a capacity issue affecting some GitHub Actions jobs in us-east-1 and have deployed a routing configuration change to address. Affected components us-east-1 (Degraded performance)
Status: Monitoring Queue times appear to have returned to normal. We will continue to monitor. Affected components us-east-1 (Operational)
Status: Identified We are seeing a recurrence of upstream capacity issues and elevated queue times for GitHub Actions jobs. We are closely monitoring and working on additional mitigations. Affected components us-east-1 (Degraded performance)
Status: Identified We are continuing to see upstream capacity issues acquiring machines for GitHub jobs. We are actively failing over to additional regions as capacity becomes available. Affected components us-east-1 (Degraded performance)
Status: Monitoring Upstream capacity appears to have recovered, and queue times have returned to normal. We will continue to monitor. Affected components us-east-1 (Operational)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Identified Experiencing periodic 502's on various pages of the depot.dev web application. Affected components Dashboard (Degraded performance)
Status: Resolved This incident has been resolved. Affected components Dashboard (Operational)
Status: Investigating We're investigating 502's occurring when trying to navigate to depot.dev and it's corresponding web application. Affected components Dashboard (Partial outage)
Status: Resolved This incident has been resolved. Affected components Dashboard (Operational)
Status: Investigating We're seeing longer queue times for Ubuntu 24.04 jobs due to upstream capacity limitations. Affected components us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Identified We have identified an issue causing a small percentage of x86 GitHub Actions jobs to fail to start and have deployed a mitigation. Affected components us-east-1 (Partial outage)
Status: Monitoring The mitigation has cleared the backlog of jobs, everything appears healthy. We will continue to monitor. Affected components us-east-1 (Operational)
Status: Monitoring We are still seeing some instability with x86 job launches - our control plane is scaling up additional capacity to compensate. Affected components us-east-1 (Degraded performance)
Status: Identified We are continuing to see reduced AWS capacity in us-east-1 and us-east-2, causing increased queue times or failures to start for some jobs. Affected components us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Investigating We are investigating reports of some GitHub runners failing to connect to GitHub Affected components us-east-1 (Partial outage)
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)
Status: Identified Failover capacity is online and job throughput is increasing. Affected components us-east-1 (Degraded performance)
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)
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)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Investigating We are investigating alerts about longer queue times for Ubuntu 24.04 x86 Actions jobs Affected components us-east-1 (Degraded performance)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)
Status: Investigating We are investigating alerts about high replication lag on Depot's primary database. Affected components Dashboard (Degraded performance) API (Degraded performance)
Status: Identified We are working with our database provider to deploy a mitigation for the increased read-replica lag. Affected components Dashboard (Degraded performance) API (Degraded performance)
Status: Resolved Mitigation is deployed, this incident has been resolved. Affected components Dashboard (Operational) API (Operational)
Status: Investigating We are investigating an issue where Windows Runners are not being assigned a machine. Affected components us-east-1 (Partial outage)
Status: Identified We have identified the issue and are working on a fix. Affected components us-east-1 (Partial outage)
Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)