Container build disruption
Depot reports a partial outage that stopped container build projects from acquiring build machines. Depot deployed a fix for the issue that prevented some container builder machines from launching. Depot states that the incident is resolved, and it lasted about 15 minutes.
State
Resolved
Started
Lasted
15 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
15 min 100%
Updates
Times in UTCAs posted by Depot
We have deployed a fix for the issue preventing some container builder machines from launching, and service is restored. This incident has been resolved.
We are investigating reports of container build projects being unable to acquire build machines.
Depot in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
31 min
This incident
51% shorter than the median
Other Depot incidents
All incidentsDepot·Increased queue times for Github Actions jobs
Depot reports that GitHub Actions jobs took longer to start in some cases. The provider identified the issue, added runner capacity, and monitored the fix. The incident is resolved, and it lasted 71 minutes.
Depot·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.
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.live/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.live/feed.xml?providers=depot/feed subscribe https://outages.live/feed.xml?providers=depotFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane