Is Crusoe Cloud down? › Outage history › May 20, 2026

Crusoe Cloud partial outage on May 20, 2026: what happened

On May 20, 2026, the Crusoe Cloud status page reported "Compute instance availability degraded in us-east1-a". About 19 hours 32 min: from May 20, 2026, 01:37 UTC to May 20, 2026, 21:09 UTC, by the official start and resolution times.

Crusoe Cloud right now

At our last refresh (Oct 22, 2026, 12:35 UTC) Crusoe Cloud was up: All Systems Operational.

Is Crusoe Cloud down right now? →
Started
May 20, 2026, 01:37 UTC
Resolved
May 20, 2026, 21:09 UTC
Duration
19 hours 32 min
Official impact
Major
Affected
us-east1, Container Registry, VPC Networking, Networking - VPC Networking, GPU Virtual Machines - us-east1, Container Registry - Container Registry
Source
Compute instance availability degraded in us-east1-a on the Crusoe Cloud status page

The Crusoe Cloud status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage.

What caused the Crusoe Cloud partial outage?

The Crusoe Cloud status page has not published a cause. When it identified the problem at 06:19 UTC on May 20, 2026, it said: "We are continuing to work on the issue affecting us-east1-a. Engineering has identified a likely cause and mitigation is in progress. A subset of compute hosts remains unavailable, and Managed Kubernetes and Container Registry operations in the region continue to be impacted. We will continue to provide updates as remediation progresses."

When was it fixed?

The Crusoe Cloud status page marked it resolved at May 20, 2026, 21:09 UTC, 19 hours 32 min after it started. Its resolution note: "This incident has been resolved. All affected compute hosts and customer virtual machines in us-east1-a have been restored."

Timeline of official updates

Every update the Crusoe Cloud status page posted, oldest first. Times are UTC.

  1. May 20, 2026, 01:37 UTC investigating

    We are investigating a networking issue in the us-east1-a region affecting connectivity to a subset of compute hosts. Affected virtual machines may appear in an unspecified state or be unreachable over the network. Managed Kubernetes clusters in the region may also report nodes as Not Ready. Container Registry operations in the region, including image push/pull and repository management, are also impacted. Engineering is engaged and actively working to identify the cause and restore service. We will provide updates as we have more information.

  2. May 20, 2026, 03:51 UTC investigating

    We are continuing to investigate this issue.

  3. May 20, 2026, 06:19 UTC identified

    We are continuing to work on the issue affecting us-east1-a. Engineering has identified a likely cause and mitigation is in progress. A subset of compute hosts remains unavailable, and Managed Kubernetes and Container Registry operations in the region continue to be impacted. We will continue to provide updates as remediation progresses.

  4. May 20, 2026, 08:25 UTC identified

    We are seeing partial recovery in us-east1-a following mitigation steps applied by engineering. A subset of affected virtual machines have returned to service. Engineering is continuing to validate the mitigation and work toward full restoration. A subset of compute hosts remains impacted at this time. We will provide further updates as progress continues.

  5. May 20, 2026, 09:28 UTC identified

    We continue to see progress in us-east1-a as engineering works through mitigation. Additional virtual machines have returned to service, although a subset of compute hosts remains impacted, and the issue is not yet fully mitigated. Engineering remains actively engaged, and we will provide further updates as recovery continues.

  6. May 20, 2026, 10:32 UTC identified

    Remediation in us-east1-a is ongoing and continuing to progress. Additional virtual machines have returned to service; however, a subset of compute hosts remains impacted and the region is not yet fully restored. Engineering remains engaged and further updates will follow.

  7. May 20, 2026, 11:28 UTC identified

    Engineering continues to work on the issue in us-east1-a. A subset of compute hosts in the region remains impacted while remediation steps are being applied. We will provide a further update once additional progress can be reported

  8. May 20, 2026, 12:37 UTC identified

    Work to restore service is ongoing as our teams continue to drive remediation in us-east1-a. Engineering remains engaged across affected compute hosts and we will provide a further update shortly.

  9. May 20, 2026, 13:27 UTC identified

    Engineering continues to make progress on the issue in us-east1-a, though recovery is proceeding more slowly than initially anticipated. A subset of compute hosts in the region remains impacted while remediation work continues. We will provide a further update as recovery advances.

  10. May 20, 2026, 14:27 UTC identified

    Work to restore service in us-east1-a continues, with engineering making steady progress across affected compute hosts. A subset of hosts remain impacted as remediation work advances. We will provide a further update shortly.

  11. May 20, 2026, 15:35 UTC identified

    Work to restore service in us-east1-a continues. Engineering has made significant progress, with the large majority of affected compute hosts now recovered. A small number of hosts remain under active remediation. We will provide a further update shortly.

  12. May 20, 2026, 16:30 UTC identified

    Engineering has restored the majority of affected services in us-east1-a and is in the final stages of remediation. A subset of customers remain impacted and are being prioritised for recovery. We will provide a further update shortly.

  13. May 20, 2026, 17:55 UTC identified

    Engineering continues to make progress on remediation since the last status post. Work remains ongoing for the customers still in progress, We will provide a further update as recovery advances.

  14. May 20, 2026, 18:55 UTC identified

    Remediation is ongoing and the number of impacted customers continues to narrow. Engineering remains actively engaged, and we will provide a further update as the work advances.

  15. May 20, 2026, 21:09 UTC resolved

    This incident has been resolved. All affected compute hosts and customer virtual machines in us-east1-a have been restored.

Crusoe Cloud partial outage questions

What caused the Crusoe Cloud partial outage on May 20, 2026?

The Crusoe Cloud status page has not published a cause. When it identified the problem (May 20, 2026, 06:19 UTC) it said: "We are continuing to work on the issue affecting us-east1-a. Engineering has identified a likely cause and mitigation is in progress. A subset of compute hosts remains unavailable, and Managed Kubernetes and Container Registry operations in the region continue to be impacted. We will continue to ..."

When was the Crusoe Cloud partial outage on May 20, 2026 fixed?

The Crusoe Cloud status page marked it resolved at May 20, 2026, 21:09 UTC, 19 hours 32 min after it started. Its resolution note: "This incident has been resolved. All affected compute hosts and customer virtual machines in us-east1-a have been restored."

How long did the Crusoe Cloud partial outage last?

About 19 hours 32 min: from May 20, 2026, 01:37 UTC to May 20, 2026, 21:09 UTC, by the official start and resolution times.

Was Crusoe Cloud completely down?

No. The Crusoe Cloud status page rated the impact "Major": a partial outage. Some parts or some users were affected; it was not a complete outage. The affected parts listed were: us-east1, Container Registry, VPC Networking, Networking - VPC Networking, GPU Virtual Machines - us-east1, Container Registry - Container Registry.

Which parts of Crusoe Cloud were affected?

The Crusoe Cloud status page listed: us-east1, Container Registry, VPC Networking, Networking - VPC Networking, GPU Virtual Machines - us-east1, Container Registry - Container Registry.

Other recent Crusoe Cloud incidents

Full Crusoe Cloud outage history and biggest outages → · Recent outages across all services →

Quotes are the Crusoe Cloud status page's own words, from the official incident. Is It Up or Down is independent and not affiliated with Crusoe Cloud. Times are UTC.