Is Devin down? › Outage history › May 29, 2026
Devin outage on May 29, 2026: what happened
On May 29, 2026, the Devin status page reported "Devin's machines are failing to start or resume". About 4 hours 22 min: from May 29, 2026, 05:27 UTC to May 29, 2026, 09:49 UTC, by the official start and resolution times.
Devin right now
At our last refresh (Oct 22, 2026, 12:35 UTC) Devin was up: All Systems Operational.
- Started
- May 29, 2026, 05:27 UTC
- Resolved
- May 29, 2026, 09:49 UTC
- Duration
- 4 hours 22 min
- Official impact
- Critical
- Affected
- Cloud Agent, Agent
- Source
- Devin's machines are failing to start or resume on the Devin status page
The Devin status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.
What caused the Devin outage?
The Devin status page has not published a cause. When it identified the problem at 05:27 UTC on May 29, 2026, it said: "The issue has been identified as an outage in an upstream provider and a fix is being implemented. Dedicated deployment enterprise sessions are not affected."
When was it fixed?
The Devin status page marked it resolved at May 29, 2026, 09:49 UTC, 4 hours 22 min after it started. A fix was in place and being monitored from May 29, 2026, 09:26 UTC.
Timeline of official updates
Every update the Devin status page posted, oldest first. Times are UTC.
May 29, 2026, 05:27 UTC identified
The issue has been identified as an outage in an upstream provider and a fix is being implemented. Dedicated deployment enterprise sessions are not affected.
May 29, 2026, 07:53 UTC identified
VM issues have been resolved. However, suspending and resuming of sessions may not work correctly at this time.
May 29, 2026, 08:01 UTC identified
We are continuing to work on a fix for this issue.
May 29, 2026, 09:26 UTC monitoring
New sessions will work properly. Sessions that started between 10 PM PT and 2:10 AM PT are affected and will still fail to save properly when suspending.
May 29, 2026, 09:49 UTC resolved
This incident has been resolved.
Devin outage questions
What caused the Devin outage on May 29, 2026?
The Devin status page has not published a cause. When it identified the problem (May 29, 2026, 05:27 UTC) it said: "The issue has been identified as an outage in an upstream provider and a fix is being implemented. Dedicated deployment enterprise sessions are not affected."
When was the Devin outage on May 29, 2026 fixed?
The Devin status page marked it resolved at May 29, 2026, 09:49 UTC, 4 hours 22 min after it started. A fix was in place and being monitored from May 29, 2026, 09:26 UTC.
How long did the Devin outage last?
About 4 hours 22 min: from May 29, 2026, 05:27 UTC to May 29, 2026, 09:49 UTC, by the official start and resolution times.
Was Devin completely down?
The Devin status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness. The affected parts listed were: Cloud Agent, Agent.
Which parts of Devin were affected?
The Devin status page listed: Cloud Agent, Agent.
Other recent Devin incidents
- Devin webapp down Sep 24, 2026, 19:59 UTC, 2 hours 3 min
- Multiple services experiencing degraded performance Sep 17, 2026, 13:40 UTC, 1 hour 40 min
- Degradation in new Devin Sessions Sep 3, 2026, 21:28 UTC, 1 hour 13 min
- Devin Cloud is unavailable Aug 13, 2026, 13:38 UTC, 2 hours 40 min
- Devin unavailable Aug 13, 2026, 03:48 UTC, 20 minutes
- Devin sessions unable to start Aug 11, 2026, 19:23 UTC, duration not stated
Full Devin outage history and biggest outages → · Recent outages across all services →
Quotes are the Devin status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Devin. Times are UTC.