Increased wait times for automation triggers
Devin had increased wait times for automation driven sessions to start. Devin implemented a fix and monitored the results. The incident is resolved and lasted 51 minutes.
State
Resolved
Started
Lasted
51 min
Worst impact
Notice
Timeline
3 updatesInvestigating
22 min 44%
Monitoring
29 min 56%
Updates
Times in UTCAs posted by Devin
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are seeing elevated wait times for automation driven sessions to start
Devin in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
8
Median duration
1 h
This incident
16% shorter than the median
Other Devin incidents
All incidentsDevin·Degraded performance in Ask Devin
This incident has been resolved.
Devin·Devin webapp down
This incident has been resolved.
Devin·Multiple services experiencing degraded performance
This incident has been resolved.
Devin·Degradation in new Devin Sessions
This incident has been resolved.
Devin·Devin Cloud is unavailable
This incident has been resolved.
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.
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.
https://outages.cc/feed.xml?providers=devin/feed subscribe https://outages.cc/feed.xml?providers=devinFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane