Builds are experiencing a slowdown.
This incident has been resolved.
The latest update from Depot.
State
Resolved
Started
65 d ago
2026-08-28 20:00 UTC
Lasted
31 min
until 2026-08-28 20:31 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
24 min 78%
Monitoring
7 min 22%
Updates
Times in UTCAs posted by Depot
This incident has been resolved.
We are seeing improvements and are monitoring.
We're seeing a slow down in builds in use-east-1 and are investigating.
Depot in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
8
Median duration
31 min
This incident
About the median
Other Depot incidents
All incidentsDepot·Delay Starting CI Jobs
This incident has been resolved.
Depot·Issue starting CI jobs
This incident has been resolved.
Depot·Slow disk I/O for US container builds
This incident has been resolved.
Depot·Slow disk I/O for EU container builds
This incident has been resolved.
Depot·Elevated queue times for Sandboxes and Depot CI Jobs
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=depot/feed subscribe https://outages.cc/feed.xml?providers=depotFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane