Depot reported "Some CI jobs failing to start" on its status page at 2026-09-20 18:09 UTC.

Depot did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-20 18:09 UTC and ended at 2026-09-20 18:14 UTC. It lasted 6 min.

How do I get alerts for Depot?

Subscribe to the Depot live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Depot. outages.live reads it every few minutes and keeps every update.

DepotIncident · 2026-09-20 18:09 UTC

Some CI jobs failing to start

ResolvedOfficial update

This incident has been resolved.

The latest update from Depot.

State

Resolved

Started

42 d ago

2026-09-20 18:09 UTC

Lasted

6 min

until 2026-09-20 18:14 UTC

Worst impact

Partial outage

Timeline

5 updates

18:0918:1018:1118:1318:14

Partial outageUpdate postedTimes in UTC

Investigating

6 min 100%

Updates

Times in UTC

As posted by Depot

Resolved2026-09-20 19:37 UTC

This incident has been resolved.

Monitoring2026-09-20 19:25 UTC

Service appears to be restored, we are continuing to monitor.

Investigating2026-09-20 18:29 UTC

We are seeing some lingering failures and are investigating.

Resolved2026-09-20 18:14 UTC

This incident has been resolved.

Investigating2026-09-20 18:09 UTC

We are investigating reports of some CI jobs failing to start.

Depot in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

31 min

This incident

82% shorter than 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 US container builds

This incident has been resolved.

Resolvedresolved 26 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

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