outages.live
Live
DepotIncident · 2026-10-06 20:14 UTC

Slow disk I/O for US container builds

ResolvedOfficial update

This incident has been resolved.

The latest update from Depot.

State

Resolved

Started

26 d ago

2026-10-06 20:14 UTC

Lasted

1 h 41 min

until 2026-10-06 21:54 UTC

Worst impact

Degraded

Timeline

2 updates
20:1420:3921:0421:2921:54
DegradedUpdate postedTimes in UTC

Monitoring

1 h 41 min 100%

Updates

Times in UTC

As posted by Depot

Resolved2026-10-06 21:54 UTC

This incident has been resolved.

Monitoring2026-10-06 20:14 UTC

Additional capacity is online and the cluster rebalance is underway. We expect build performance to have returned to normal, but will keep monitoring until the cluster has completed rebalancing.

Depot in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

8

Median duration

31 min

This incident

3.3× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 2 min
median 31 min
90 days agoToday

Other Depot incidents

All incidents

Depot·Delay Starting CI Jobs

This incident has been resolved.

Resolvedresolved 2 d ago

Depot·Issue starting CI jobs

This incident has been resolved.

Resolvedresolved 24 d ago

Depot·Slow disk I/O for EU container builds

This incident has been resolved.

Resolvedresolved 27 d ago

Depot·Elevated queue times for Sandboxes and Depot CI Jobs

This incident has been resolved.

Resolvedresolved 34 d ago

Depot·Some CI jobs failing to start

This incident has been resolved.

Resolvedresolved 42 d ago

Follow Depot

Your coding agent knows when Depot is down, and tells you when a failure is theirs, not yours. You can also get Depot incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "depot" and tell me if Depot has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=depot
Slack
/feed subscribe https://outages.cc/feed.xml?providers=depot

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane