Is Crusoe Cloud down? › Outage history › Oct 15, 2026

Crusoe Cloud outage on Oct 15, 2026: what happened

On Oct 15, 2026, the Crusoe Cloud status page reported "Facility issue in us-east2-a". About 3 days 7 hours: from Oct 15, 2026, 13:12 UTC to Oct 18, 2026, 20:22 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: Oct 15, 2026, 13:12 UTC
Resolved: Oct 18, 2026, 20:22 UTC
Duration: 3 days 7 hours
Official impact: Critical
Affected: us-east2, Datacenter Networking, GPU Virtual Machines - us-east2, Networking - Datacenter Networking, Storage - Shared Disks
Source: Facility issue in us-east2-a on the Crusoe Cloud status page

The Crusoe Cloud status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness.

What caused the Crusoe Cloud outage?

The Crusoe Cloud status page has not published a cause. When it identified the problem at 16:03 UTC on Oct 15, 2026, it said: "We've started restoring power to part of the affected hardware in us-east2-a, and some instances will begin to come back online. The rest of the affected hardware will stay powered off while the facility issue is being remediated. Our teams are actively working on recovery, and we'll post updates as events warrant."

When was it fixed?

The Crusoe Cloud status page marked it resolved at Oct 18, 2026, 20:22 UTC, 3 days 7 hours after it started.

Timeline of official updates

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

Oct 15, 2026, 13:12 UTC investigating
We're investigating an issue at one of our data center facilities that is affecting a subset of compute instances in us-east2-a. Some instances are currently unavailable. As a safety precaution, we're powering down some additional hardware in the affected area. Instances on that hardware will become unavailable during this time. Our teams are actively working on this, and we'll post another update within 30 minutes.
Oct 15, 2026, 13:50 UTC investigating
As a safety precaution, we've shut off power to the affected hardware in us-east2-a. Instances running on that hardware are now powered off. Power won't be restored until the area has been confirmed safe. Our teams are working on recovery, and we'll post another update within 90 minutes.
Oct 15, 2026, 16:03 UTC identified
We've started restoring power to part of the affected hardware in us-east2-a, and some instances will begin to come back online. The rest of the affected hardware will stay powered off while the facility issue is being remediated. Our teams are actively working on recovery, and we'll post updates as events warrant.
Oct 15, 2026, 19:20 UTC identified
Recovery work for the facility issue in us-east2-a is ongoing. The remaining affected hardware will stay powered off until required facility work and safety inspections are complete. We don't have an estimated restoration time yet, and we'll share one as soon as those inspections are done. In the meantime, we're restoring affected instances on other available capacity in us-east2-a where possible, and a number of instances are already back online. If your instances are affected, our customer success team is in contact with you directly. We'll post another update by 23:00 UTC
Oct 16, 2026, 00:59 UTC identified
Work to address the facility issue in us-east2-a continues to progress. The hardware that's still affected will stay offline until facility repairs and safety checks are finished, and we don't yet have a time for full restoration. Our teams are still moving impacted instances onto other available capacity in us-east2-a where we can. We will post updates on further developments within the next 24 hours.
Oct 16, 2026, 07:22 UTC identified
We have restored part of the affected capacity in us-east2-a and continue to move impacted instances onto other available capacity where we can. The remaining affected hardware will stay offline until facility repairs and safety checks are finished, and we don't yet have a time for full restoration. We will post an update in 24 hours, or as events warrant.
Oct 16, 2026, 14:48 UTC identified
Work to address the facility issue in us-east2-a continues. The affected hardware will stay offline until facility repairs and safety checks are complete, and it will be brought back online as that work allows. We don't yet have a time for full restoration. Our teams continue to move impacted instances onto other available capacity in us-east2-a where we can. We will post an update in 24 hours, or as events warrant.
Oct 17, 2026, 07:16 UTC identified
We have restored additional capacity in us-east2-a and are validating each host before returning it to service. Some affected customers are now fully restored, and we continue to return capacity to the remaining impacted customers. The remaining affected hardware will stay offline until facility repairs and safety checks are finished, and we don't yet have a time for full restoration. We will post an update in 24 hours, or as events warrant.
Oct 18, 2026, 16:51 UTC identified
Most affected instances in our Ohio region are back in service. A small number are still unavailable while we finish hardware checks and the last repairs. We'll keep you posted on further developments
Oct 18, 2026, 20:22 UTC resolved
This incident has been resolved.

What our checks saw

Our once-a-minute checks recorded Crusoe Cloud as degraded from Oct 15, 2026, 13:22 UTC to 20:38 UTC on Oct 18, 2026 (3 days 7 hours, read from the official status page).

Crusoe Cloud outage questions

What caused the Crusoe Cloud outage on Oct 15, 2026?

The Crusoe Cloud status page has not published a cause. When it identified the problem (Oct 15, 2026, 16:03 UTC) it said: "We've started restoring power to part of the affected hardware in us-east2-a, and some instances will begin to come back online. The rest of the affected hardware will stay powered off while the facility issue is being remediated. Our teams are actively working on recovery, and we'll post updates ..."

When was the Crusoe Cloud outage on Oct 15, 2026 fixed?

The Crusoe Cloud status page marked it resolved at Oct 18, 2026, 20:22 UTC, 3 days 7 hours after it started.

How long did the Crusoe Cloud outage last?

About 3 days 7 hours: from Oct 15, 2026, 13:12 UTC to Oct 18, 2026, 20:22 UTC, by the official start and resolution times.

Was Crusoe Cloud completely down?

The Crusoe Cloud status page rated it "Critical", its highest impact level: an outage of the affected parts, not only slowness. The affected parts listed were: us-east2, Datacenter Networking, GPU Virtual Machines - us-east2, Networking - Datacenter Networking, Storage - Shared Disks.

Which parts of Crusoe Cloud were affected?

The Crusoe Cloud status page listed: us-east2, Datacenter Networking, GPU Virtual Machines - us-east2, Networking - Datacenter Networking, Storage - Shared Disks.

Other recent Crusoe Cloud incidents

Storage accessibility issues in eu-norway1 Sep 29, 2026, 20:38 UTC, 3 hours 54 min
A subset of VMs are showing as UNSPECIFIED in our us-east2 region Sep 9, 2026, 09:56 UTC, 1 hour 22 min
Networking issue affecting service connectivity Sep 3, 2026, 12:30 UTC, duration not stated
VM and CMK cluster creation issue in us-east2 region Sep 2, 2026, 08:22 UTC, 7 hours 35 min
Degraded Network Connectivity in us-east-1-a region Jul 9, 2026, 14:45 UTC, 2 hours 13 min
Crusoe Container Registry (CCR) Outage - TLS/Auth Errors in US South Central(us-southcentral1-a) Jul 8, 2026, 05:23 UTC, 34 hours

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.