Depot Outage History

Depot is up right now

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.

Source: https://status.depot.dev

Minor June 17, 2026

Increased queue times for GitHub Actions jobs

Detected by Pingoru
Jun 17, 2026, 02:23 PM UTC
Resolved
Jun 17, 2026, 02:23 PM UTC
Duration
Affected: us-east-1
Timeline · 2 updates
  1. investigating Jun 17, 2026, 02:13 PM UTC

    Status: Investigating We are investigating increased queue times for GitHub Actions jobs Affected components us-east-1 (Degraded performance)

  2. resolved Jun 17, 2026, 02:23 PM UTC

    Status: Resolved This incident has been resolved, all jobs are processing normally. Affected components us-east-1 (Operational)

Read the full incident report →

Minor June 9, 2026

GitHub Actions runner disconnections

Detected by Pingoru
Jun 09, 2026, 07:13 PM UTC
Resolved
Jun 09, 2026, 07:13 PM UTC
Duration
Affected: GitHub.com
Timeline · 3 updates
  1. investigating Jun 09, 2026, 06:31 PM UTC

    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)

  2. monitoring Jun 09, 2026, 06:46 PM UTC

    Status: Monitoring We have deployed a mitigation for the disconnect and are monitoring Affected components GitHub.com (Operational)

  3. resolved Jun 09, 2026, 07:13 PM UTC

    Status: Resolved This incident is resolved Affected components GitHub.com (Operational)

Read the full incident report →

Minor May 29, 2026

GitHub jobs using Depot managed are unable to start

Detected by Pingoru
May 29, 2026, 12:28 AM UTC
Resolved
May 29, 2026, 12:28 AM UTC
Duration
Affected: us-east-1
Timeline · 3 updates
  1. investigating May 28, 2026, 11:04 PM UTC

    Status: Investigating GitHub jobs using Depot managed are unable to start. Affected components us-east-1 (Partial outage)

  2. monitoring May 29, 2026, 12:21 AM UTC

    Status: Monitoring We've applied a fix and are monitoring Affected components us-east-1 (Operational)

  3. resolved May 29, 2026, 12:28 AM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor May 29, 2026

Depot CI jobs not syncing checks to GitHub

Detected by Pingoru
May 29, 2026, 12:26 AM UTC
Resolved
May 29, 2026, 12:26 AM UTC
Duration
Affected: Depot CI
Timeline · 3 updates
  1. identified May 29, 2026, 12:07 AM UTC

    Status: Identified Depot CI jobs not syncing checks to GitHub. Affected components Depot CI (Degraded performance)

  2. monitoring May 29, 2026, 12:21 AM UTC

    Status: Monitoring We've applied a fix and are monitoring. Affected components Depot CI (Operational)

  3. resolved May 29, 2026, 12:26 AM UTC

    Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)

Read the full incident report →

Minor May 28, 2026

Depot CI has higher queue times

Detected by Pingoru
May 28, 2026, 10:48 PM UTC
Resolved
May 28, 2026, 10:48 PM UTC
Duration
Affected: Depot CI
Timeline · 2 updates
  1. investigating May 28, 2026, 10:32 PM UTC

    Status: Investigating We are seeing high queue times and are scaling up. Affected components Depot CI (Degraded performance)

  2. resolved May 28, 2026, 10:48 PM UTC

    Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)

Read the full incident report →

Minor May 26, 2026

Delays starting GitHub jobs

Detected by Pingoru
May 26, 2026, 02:47 PM UTC
Resolved
May 26, 2026, 02:47 PM UTC
Duration
Affected: us-east-1
Timeline · 3 updates
  1. identified May 26, 2026, 02:23 PM UTC

    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)

  2. identified May 26, 2026, 02:28 PM UTC

    Status: Identified Fix is deployed, we are processing the backlog of jobs now Affected components us-east-1 (Degraded performance)

  3. resolved May 26, 2026, 02:47 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor May 18, 2026

slow container builds in us-east-1 for some customers

Detected by Pingoru
May 18, 2026, 09:23 PM UTC
Resolved
May 18, 2026, 09:23 PM UTC
Duration
Affected: us-east-1
Timeline · 3 updates
  1. identified May 18, 2026, 09:04 PM UTC

    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)

  2. monitoring May 18, 2026, 09:10 PM UTC

    Status: Monitoring We are seeing recovery now and new builds are having normal disk i/o. Affected components us-east-1 (Degraded performance)

  3. resolved May 18, 2026, 09:23 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor May 17, 2026

Some Depot CI jobs failing to start

Detected by Pingoru
May 17, 2026, 09:21 AM UTC
Resolved
May 17, 2026, 09:21 AM UTC
Duration
Affected: Depot CI
Timeline · 5 updates
  1. investigating May 17, 2026, 08:11 AM UTC

    Status: Investigating We are investigating an issue preventing some Depot CI jobs from starting. Affected components Depot CI (Partial outage)

  2. monitoring May 17, 2026, 08:21 AM UTC

    Status: Monitoring We have deployed a fix and jobs are processing. We are continuing to monitor. Affected components Depot CI (Operational)

  3. identified May 17, 2026, 08:28 AM UTC

    Status: Identified We are still seeing some intermittent failures and are investigating. Affected components Depot CI (Partial outage)

  4. monitoring May 17, 2026, 09:02 AM UTC

    Status: Monitoring Jobs are processing again, we are continuing to monitor. Affected components Depot CI (Operational)

  5. resolved May 17, 2026, 09:21 AM UTC

    Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)

Read the full incident report →

Minor May 14, 2026

Unable to start some Depot CI jobs

Detected by Pingoru
May 14, 2026, 09:41 PM UTC
Resolved
May 14, 2026, 09:41 PM UTC
Duration
Affected: Depot CI
Timeline · 3 updates
  1. investigating May 14, 2026, 09:05 PM UTC

    Status: Investigating Investigating the failure of some Depot CI jobs being able to start. Affected components Depot CI (Partial outage)

  2. monitoring May 14, 2026, 09:36 PM UTC

    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)

  3. resolved May 14, 2026, 09:41 PM UTC

    Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)

Read the full incident report →

Minor May 13, 2026

Job's relying on OIDC are unable to be authenticated

Detected by Pingoru
May 13, 2026, 08:56 PM UTC
Resolved
May 13, 2026, 08:56 PM UTC
Duration
Affected: Depot CI
Timeline · 2 updates
  1. identified May 13, 2026, 08:16 PM UTC

    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)

  2. resolved May 13, 2026, 08:56 PM UTC

    Status: Resolved This has been resolved. Affected components Depot CI (Operational)

Read the full incident report →

Minor May 13, 2026

Depot CI Jobs are experiencing higher queue times

Detected by Pingoru
May 13, 2026, 07:13 PM UTC
Resolved
May 13, 2026, 07:13 PM UTC
Duration
Affected: Depot CI
Timeline · 3 updates
  1. investigating May 13, 2026, 06:35 PM UTC

    Status: Investigating We are investigating higher queue times for Depot CI jobs. Affected components Depot CI (Degraded performance)

  2. monitoring May 13, 2026, 07:07 PM UTC

    Status: Monitoring We've deployed a fix and are monitoring recovery. Affected components Depot CI (Operational)

  3. resolved May 13, 2026, 07:13 PM UTC

    Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)

Read the full incident report →

Minor May 4, 2026

GitHub API Outage

Detected by Pingoru
May 04, 2026, 04:48 PM UTC
Resolved
May 04, 2026, 04:48 PM UTC
Duration
Affected: GitHub.com
Timeline · 3 updates
  1. investigating May 04, 2026, 04:05 PM UTC

    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)

  2. monitoring May 04, 2026, 04:38 PM UTC

    Status: Monitoring GitHub has indicated that their incident has been mitigated. We'll continue to monitor the situation. Affected components GitHub.com (Operational)

  3. resolved May 04, 2026, 04:48 PM UTC

    Status: Resolved This incident has been resolved. Affected components GitHub.com (Operational)

Read the full incident report →

Minor April 23, 2026

Missing logs and metrics for Jobs

Detected by Pingoru
Apr 23, 2026, 09:03 PM UTC
Resolved
Apr 23, 2026, 09:03 PM UTC
Duration
Affected: Depot CIus-east-1
Timeline · 5 updates
  1. investigating Apr 23, 2026, 07:57 PM UTC

    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)

  2. identified Apr 23, 2026, 08:14 PM UTC

    Status: Identified Identified the issue and working on a fix. Affected components us-east-1 (Degraded performance) Depot CI (Operational)

  3. investigating Apr 23, 2026, 08:19 PM UTC

    Status: Investigating We are investigating. Affected components us-east-1 (Degraded performance) Depot CI (Degraded performance)

  4. monitoring Apr 23, 2026, 08:49 PM UTC

    Status: Monitoring We've applied a fix and are monitoring. Affected components us-east-1 (Operational) Depot CI (Operational)

  5. resolved Apr 23, 2026, 09:03 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational) Depot CI (Operational)

Read the full incident report →

Minor April 16, 2026

Database Outage

Detected by Pingoru
Apr 16, 2026, 01:50 AM UTC
Resolved
Apr 16, 2026, 01:50 AM UTC
Duration
Affected: APIDepot CIDepot CacheContainer Registryus-east-1eu-central-1Dashboard
Timeline · 4 updates
  1. investigating Apr 16, 2026, 01:06 AM UTC

    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)

  2. identified Apr 16, 2026, 01:24 AM UTC

    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)

  3. identified Apr 16, 2026, 01:34 AM UTC

    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)

  4. resolved Apr 16, 2026, 01:50 AM UTC

    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)

Read the full incident report →

Minor April 14, 2026

High number of failed of early sandbox termination

Detected by Pingoru
Apr 14, 2026, 11:11 PM UTC
Resolved
Apr 14, 2026, 11:11 PM UTC
Duration
Affected: Depot CI
Timeline · 2 updates
  1. investigating Apr 14, 2026, 10:41 PM UTC

    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)

  2. resolved Apr 14, 2026, 11:11 PM UTC

    Status: Resolved This incident has been resolved. Affected components Depot CI (Operational)

Read the full incident report →

Minor April 8, 2026

Increased Ubuntu x86 job queue time

Detected by Pingoru
Apr 08, 2026, 08:57 PM UTC
Resolved
Apr 08, 2026, 08:57 PM UTC
Duration
Affected: us-east-1
Timeline · 4 updates
  1. investigating Apr 08, 2026, 04:25 PM UTC

    Status: Investigating We are investigating reports of increased queue time for x86 Ubuntu GitHub Actions jobs. Affected components us-east-1 (Degraded performance)

  2. identified Apr 08, 2026, 07:26 PM UTC

    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)

  3. monitoring Apr 08, 2026, 08:30 PM UTC

    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)

  4. resolved Apr 08, 2026, 08:57 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor April 7, 2026

Increased queue time for GitHub Actions jobs

Detected by Pingoru
Apr 07, 2026, 11:55 PM UTC
Resolved
Apr 07, 2026, 11:55 PM UTC
Duration
Affected: us-east-1
Timeline · 6 updates
  1. identified Apr 07, 2026, 06:56 PM UTC

    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)

  2. monitoring Apr 07, 2026, 07:10 PM UTC

    Status: Monitoring Queue times appear to have returned to normal. We will continue to monitor. Affected components us-east-1 (Operational)

  3. identified Apr 07, 2026, 07:25 PM UTC

    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)

  4. identified Apr 07, 2026, 08:45 PM UTC

    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)

  5. monitoring Apr 07, 2026, 10:18 PM UTC

    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)

  6. resolved Apr 07, 2026, 11:55 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor March 30, 2026

depot.dev app 502

Detected by Pingoru
Mar 30, 2026, 10:51 PM UTC
Resolved
Mar 30, 2026, 10:51 PM UTC
Duration
Affected: Dashboard
Timeline · 2 updates
  1. identified Mar 30, 2026, 10:42 PM UTC

    Status: Identified Experiencing periodic 502's on various pages of the depot.dev web application. Affected components Dashboard (Degraded performance)

  2. resolved Mar 30, 2026, 10:51 PM UTC

    Status: Resolved This incident has been resolved. Affected components Dashboard (Operational)

Read the full incident report →

Minor March 30, 2026

Depot.dev appears with occasional 502

Detected by Pingoru
Mar 30, 2026, 09:01 PM UTC
Resolved
Mar 30, 2026, 09:01 PM UTC
Duration
Affected: Dashboard
Timeline · 2 updates
  1. investigating Mar 30, 2026, 08:41 PM UTC

    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)

  2. resolved Mar 30, 2026, 09:01 PM UTC

    Status: Resolved This incident has been resolved. Affected components Dashboard (Operational)

Read the full incident report →

Minor March 26, 2026

Longer queue times for Ubuntu 24.04 jobs

Detected by Pingoru
Mar 26, 2026, 05:47 PM UTC
Resolved
Mar 26, 2026, 05:47 PM UTC
Duration
Affected: us-east-1
Timeline · 2 updates
  1. investigating Mar 26, 2026, 05:38 PM UTC

    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)

  2. resolved Mar 26, 2026, 05:47 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor March 19, 2026

Intermittent failures for GitHub Actions x86 jobs

Detected by Pingoru
Mar 19, 2026, 06:28 PM UTC
Resolved
Mar 19, 2026, 06:28 PM UTC
Duration
Affected: us-east-1
Timeline · 5 updates
  1. identified Mar 19, 2026, 03:02 PM UTC

    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)

  2. monitoring Mar 19, 2026, 03:04 PM UTC

    Status: Monitoring The mitigation has cleared the backlog of jobs, everything appears healthy. We will continue to monitor. Affected components us-east-1 (Operational)

  3. monitoring Mar 19, 2026, 03:10 PM UTC

    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)

  4. identified Mar 19, 2026, 03:44 PM UTC

    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)

  5. resolved Mar 19, 2026, 06:28 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor March 9, 2026

Some GitHub jobs failing to connect

Detected by Pingoru
Mar 09, 2026, 04:30 PM UTC
Resolved
Mar 09, 2026, 04:30 PM UTC
Duration
Affected: us-east-1
Timeline · 6 updates
  1. 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)

  2. 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)

  3. 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)

  4. 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)

  5. 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)

  6. resolved Mar 09, 2026, 04:30 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor March 3, 2026

Longer queue times for Ubuntu 24.04 Actions jobs

Detected by Pingoru
Mar 03, 2026, 03:32 PM UTC
Resolved
Mar 03, 2026, 03:32 PM UTC
Duration
Affected: us-east-1
Timeline · 2 updates
  1. investigating Mar 03, 2026, 03:09 PM UTC

    Status: Investigating We are investigating alerts about longer queue times for Ubuntu 24.04 x86 Actions jobs Affected components us-east-1 (Degraded performance)

  2. resolved Mar 03, 2026, 03:32 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →

Minor March 1, 2026

Database performance issues

Detected by Pingoru
Mar 01, 2026, 08:02 PM UTC
Resolved
Mar 01, 2026, 08:02 PM UTC
Duration
Affected: APIDashboard
Timeline · 3 updates
  1. investigating Mar 01, 2026, 07:04 PM UTC

    Status: Investigating We are investigating alerts about high replication lag on Depot's primary database. Affected components Dashboard (Degraded performance) API (Degraded performance)

  2. identified Mar 01, 2026, 07:41 PM UTC

    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)

  3. resolved Mar 01, 2026, 08:02 PM UTC

    Status: Resolved Mitigation is deployed, this incident has been resolved. Affected components Dashboard (Operational) API (Operational)

Read the full incident report →

Minor February 26, 2026

Unable to provision Windows runners.

Detected by Pingoru
Feb 26, 2026, 08:34 PM UTC
Resolved
Feb 26, 2026, 08:34 PM UTC
Duration
Affected: us-east-1
Timeline · 3 updates
  1. investigating Feb 26, 2026, 08:11 PM UTC

    Status: Investigating We are investigating an issue where Windows Runners are not being assigned a machine. Affected components us-east-1 (Partial outage)

  2. identified Feb 26, 2026, 08:28 PM UTC

    Status: Identified We have identified the issue and are working on a fix. Affected components us-east-1 (Partial outage)

  3. resolved Feb 26, 2026, 08:34 PM UTC

    Status: Resolved This incident has been resolved. Affected components us-east-1 (Operational)

Read the full incident report →