Devin incident

Starting Devin sessions degraded

Major Resolved View vendor source →

Devin experienced a major incident on February 5, 2026 affecting Cloud Agent, lasting 1h 24m. The incident has been resolved; the full update timeline is below.

Started
Feb 05, 2026, 04:28 PM UTC
Resolved
Feb 05, 2026, 05:53 PM UTC
Duration
1h 24m
Detected by Pingoru
Feb 05, 2026, 04:28 PM UTC

Affected components

Cloud Agent

Update timeline

  1. investigating Feb 05, 2026, 04:28 PM UTC

    Due to spikes in demand, Devins are slow to start. Some Devins are being started in a degraded state. We are currently investigating the issue.

  2. investigating Feb 05, 2026, 04:48 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 05, 2026, 05:10 PM UTC

    We are continuing to investigate this issue. We are seeing continued delays when starting Devin sessions.

  4. identified Feb 05, 2026, 05:22 PM UTC

    We have identified a root cause and have applied a mitigation. There is a large backlog of session requests so slowness is still expected. We are working on accelerating draining the queue.

  5. monitoring Feb 05, 2026, 05:27 PM UTC

    A patch to accelerate draining of the queue has been applied. At this moment, we expect the system to be fully operational, but will continue to monitor.

  6. resolved Feb 05, 2026, 05:53 PM UTC

    This incident has been resolved.