Live

Devin sessions queued

Devin sessions queued for users for up to 12 minutes.

The latest update from Devin.

State

Resolved

Started

83 d ago

2026-08-10 14:45 UTC

Lasted

1 min

until 2026-08-10 14:45 UTC

Worst impact

Partial outage

Timeline

1 update
14:4514:4514:4514:4514:46
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Devin

Resolved2026-08-10 14:45 UTC

Devin sessions queued for users for up to 12 minutes.

Devin in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

8

Days with an incident

7

Median duration

1 h 7 min

This incident

100% shorter than the median

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

2 h 40 min
median 1 h 7 min
90 days agoToday

Other Devin incidents

All incidents

Follow Devin

Your coding agent knows when Devin is down, and tells you when a failure is theirs, not yours. You can also get Devin 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 "devin" and tell me if Devin 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=devin
Slack
/feed subscribe https://outages.cc/feed.xml?providers=devin

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane