outages.live
Live
DepotIncident ·

Increased queue times for Github Actions jobs

ResolvedOfficial update
0

GitHub Actions jobs had longer queue times in some cases. Depot reports that the incident is resolved. The incident lasted 1 hour and 11 minutes.

State

Resolved

Started

Lasted

1 h 11 min

Worst impact

Degraded

Timeline

4 updates
18:3918:5719:1519:3219:50
DegradedUpdate postedTimes in UTC

Investigating

38 min 54%

Identified

27 min 38%

Monitoring

5 min 8%

Updates

Times in UTC

As posted by Depot

Resolved

This incident has been resolved.

Monitoring

We are observing normal queue times for GitHub Actions jobs. We will continue to monitor.

Identified

We have identified the issue slowing the launch of new runner instances and have activated additional runner capacity to address.

Investigating

Github Actions jobs are taking longer to start in some cases.

Depot in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

9

Median duration

51 min

This incident

1.4× the median

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

3 h 2 min
median 51 min
90 days agoToday

Other Depot incidents

All incidents

Depot·Delay Starting CI Jobs

This incident has been resolved.

Resolved

Depot·Issue starting CI jobs

This incident has been resolved.

Resolved

Depot·Slow disk I/O for US container builds

This incident has been resolved.

Resolved

Depot·Slow disk I/O for EU container builds

This incident has been resolved.

Resolved

Depot·Elevated queue times for Sandboxes and Depot CI Jobs

This incident has been resolved.

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.

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