Crusoe incident

VM and CMK cluster creation issue in us-east2 region

Minor Resolved View vendor source →

Crusoe experienced a minor incident on September 2, 2026, lasting 7h 35m. The incident has been resolved; the full update timeline is below.

Started
Sep 02, 2026, 08:22 AM UTC
Resolved
Sep 02, 2026, 03:57 PM UTC
Duration
7h 35m
Detected by Pingoru
Sep 02, 2026, 08:22 AM UTC

Update timeline

  1. investigating Sep 02, 2026, 08:22 AM UTC

    We are investigating "insufficient capacity" errors when creating VMs or CMK clusters in us-east2 region. Existing VMs continue to run normally. We'll share an update as soon as we have more information available.

  2. investigating Sep 02, 2026, 09:44 AM UTC

    We continue investigating "insufficient capacity" errors when creating VMs or CMK clusters in us-east2 region, and have narrowed down a likely cause. We'll share an update as soon as we have more information available.

  3. investigating Sep 02, 2026, 11:07 AM UTC

    We continue investigating "insufficient capacity" errors when creating VMs or CMK clusters in us-east2 region. We'll share an update as soon as we have more information available.

  4. investigating Sep 02, 2026, 12:56 PM UTC

    We continue investigating "insufficient capacity" errors when creating/starting VMs or creating scaling CMK clusters in us-east2 region. We'll share an update as soon as we have more information available.

  5. monitoring Sep 02, 2026, 01:40 PM UTC

    We've identified the cause of the errors when creating/starting VMs or creating scaling CMK clusters in us-east2 region and applied a fix. We'll continue monitoring.

  6. resolved Sep 02, 2026, 03:57 PM UTC

    This incident has been resolved.