Crusoe

Affected: us-east2, Datacenter Networking

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-15 13:12 UTC

   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...

2. investigating 2026-10-15 13:50 UTC

   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...

3. identified 2026-10-15 16:03 UTC

   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...

4. identified 2026-10-15 19:20 UTC

   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...

5. identified 2026-10-16 00:59 UTC

   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...

6. identified 2026-10-16 07:22 UTC

   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...

7. identified 2026-10-16 14:48 UTC

   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...

8. identified 2026-10-17 07:16 UTC

   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...

9. identified 2026-10-18 16:51 UTC

   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

10. resolved 2026-10-18 20:22 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-29 20:38 UTC

   We are currently investigating storage accessibility issues when using Shared Storage, Object Storage and Crusoe Container Registry in eu-norway1. We are working with our storage vendor to resolve the issue as soon as possible and will keep you posted on further developments.

2. identified 2026-09-29 21:18 UTC

   We are seeing early signs of recovery for Shared Storage, Object Storage and Crusoe Container Registry in eu-norway1. We are still working closely with our storage vendor to fully restore service and will share another update as progress continues.

3. monitoring 2026-09-29 23:43 UTC

   Shared Storage, Object Storage and Crusoe Container Registry in eu-norway1 are available again. We have put a fix in place with our storage vendor and are monitoring the results. We will share another update once we confirm the service is stable.

4. resolved 2026-09-30 00:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east2

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-09 09:56 UTC

   We're currently investigating an issue affecting a subset of customer VMs in our us-east2 region . A subset of VMs are showing as UNSPECIFIED in our control plane . We have identified the issue and are actively working on fixing it to bring affected VMs back to a healthy state....

2. monitoring 2026-09-09 10:51 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-09 11:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-03 12:30 UTC

   We identified general network errors affecting service connectivity in our us-east1 region. The issue has been resolved and services are operating normally.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 08:22 UTC

   We are investigating "insufficient capacity" errors when creating/starting VMs or creating scaling 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 2026-09-02 09:44 UTC

   We continue investigating "insufficient capacity" errors when creating/starting VMs or creating scaling 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 2026-09-02 11:07 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.

4. investigating 2026-09-02 12:56 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 2026-09-02 13:40 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 2026-09-02 15:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Datacenter Networking

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-09 14:45 UTC

   We are currently investigating reports of degraded network connectivity in our us-east-1-a region. Some customers may be experiencing connection timeouts, SSL handshake failures, or degraded network performance for workloads hosted in this region. Our engineers are actively...

2. investigating 2026-07-09 15:10 UTC

   We have implemented a fix for the network connectivity issues affecting us-east-1-a. We are seeing improvements across impacted services and are actively monitoring the environment to confirm full recovery. We will provide a further update once we have verified complete...

3. monitoring 2026-07-09 15:12 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-09 16:58 UTC

   This incident has been resolved. Network connectivity in our us-east-1-a region has been fully restored. We sincerely apologize for any disruption this may have caused and thank you for your patience.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Container Registry

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-08 05:23 UTC

   We are investigating an issue affecting the Crusoe Container Registry (CCR) in the US South Central (us-southcentral1-a) region. Beginning at approximately 04:07 UTC on July 8, 2026, customers may be unable to push or pull container images, and may see TLS handshake timeouts or...

2. investigating 2026-07-08 11:03 UTC

   We continue to investigate the issue and have narrowed down the root cause. Our team is actively working towards a resolution and will provide a further update as soon as possible.

3. monitoring 2026-07-08 21:57 UTC

   We have applied a fix which looks to have mitigated the issue. Please let us know if you are still seeing an issue. We are continuing to monitor.

4. resolved 2026-07-09 15:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-25 09:30 UTC

   A subset of resources in us-east1-a experienced intermittent external connectivity disruption during a planned network maintenance window. Affected workloads may have observed elevated latency, connection timeouts, or failures reaching external destinations. Virtual machine...

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Datacenter Networking

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-16 21:15 UTC

   Beginning at approximately 13:55 PDT, load balancers in the ICAT region became unreachable. Customers relying on load balancer endpoints in this region may be experiencing connectivity failures. Our team is actively investigating and working to restore service. We will provide...

2. investigating 2026-06-17 01:17 UTC

   The issue was identified and resolved as of approximately 15:45 PDT. Load balancer connectivity in the ICAT region has been restored.

3. resolved 2026-06-17 01:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1, us-southcentral1, eu-iceland1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-11 16:50 UTC

   We have identified an issue affecting custom image creation in us-east1-a, us-southcentral1-a and eu-iceland1-a regions. We have identified the underlying cause and are actively working to restore service. We will provide more information as soon as possible.

2. identified 2026-06-11 16:51 UTC

   The issue has been identified and a fix is being implemented.

3. resolved 2026-06-11 19:47 UTC

   This issue is now resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Wide Area Networking (WAN), VPC Networking, Datacenter Networking

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-08 22:12 UTC

   We are seeing a network outage in this region, which is currently under investigation. We will keep you posted on further developments as we make progress on this matter

2. monitoring 2026-06-08 23:41 UTC

   A fix has been implemented and we are monitoring. Please let us know if you are still seeing any network related performance issues. We will keep you updated with any further developments.

3. resolved 2026-06-09 14:56 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: VPC Networking

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-04 02:10 UTC

   We are seeing intermittent network degradation in this region, which is currently under investigation. We will keep you posted on further developments as we make progress on this matter

2. monitoring 2026-06-04 03:31 UTC

   We are now monitoring the incident and if you see any issues, please reach out to support.

3. resolved 2026-06-04 04:27 UTC

   This issue is now resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks, eu-iceland1

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-25 12:32 UTC

   We are investigating an issue on the eu-iceland1-storage cluster. Customers may experience elevated write latency. We will provide an update as soon as we have more information available.

2. investigating 2026-05-25 13:08 UTC

   We are continuing to investigate this issue.

3. investigating 2026-05-25 14:28 UTC

   We are continuing to investigate this issue.

4. identified 2026-05-25 15:15 UTC

   We are seeing an improvement in latency and our teams remain fully focused on driving further recovery. We will provide an update as soon as we have more information available.

5. resolved 2026-05-26 00:26 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1, Container Registry, VPC Networking

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-20 01:37 UTC

   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...

2. investigating 2026-05-20 03:51 UTC

   We are continuing to investigate this issue.

3. identified 2026-05-20 06:19 UTC

   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...

4. identified 2026-05-20 08:25 UTC

   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...

5. identified 2026-05-20 09:28 UTC

   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...

6. identified 2026-05-20 10:32 UTC

   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. identified 2026-05-20 11:28 UTC

   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. identified 2026-05-20 12:37 UTC

   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. identified 2026-05-20 13:27 UTC

   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...

10. identified 2026-05-20 14:27 UTC

    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. identified 2026-05-20 15:35 UTC

    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. identified 2026-05-20 16:30 UTC

    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. identified 2026-05-20 17:55 UTC

    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. identified 2026-05-20 18:55 UTC

    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. resolved 2026-05-20 21:09 UTC

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

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-southcentral1, eu-iceland1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-18 08:24 UTC

   We are investigating an issue affecting the ability to create and start Virtual Machines in the us-southcentral1-a and eu-iceland1-a regions. Existing running workloads and resources remain fully operational and are not impacted. Our Engineering teams are actively working on...

2. identified 2026-05-18 11:27 UTC

   We have identified the underlying issue affecting the ability to create and start Virtual Machines in the us-southcentral1-a and eu-iceland1-a regions. Our Engineering teams are actively working on recovery. Some customers may still be experiencing impact while this work...

3. monitoring 2026-05-18 14:34 UTC

   The issue affecting the ability to create and start Virtual Machines in the us-southcentral1-a and eu-iceland1-a regions has been mitigated. VM creation and start operations are functioning normally. No customer impact has been observed as of 14:00 UTC. Our Engineering teams...

4. resolved 2026-05-19 01:19 UTC

   VM creation and start operations in the us-southcentral1-a and eu-iceland1-a regions have been functioning normally for several hours. Our Engineering teams have addressed the underlying issue and a permanent fix is being prepared for deployment to prevent recurrence. Existing...

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Container Registry

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-13 21:34 UTC

   Customers using CCR (Crusoe Container Registry) will be unable to push or pull images. We are working on resolving this matter as soon as possible. If you experience any other issues, please reach out to support@crusoe.ai

2. resolved 2026-05-14 00:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-10 14:41 UTC

   We are investigating an issue affecting access to Crusoe Managed Inference, including Intelligence Foundry and Bring Your Own Model (BYOM). Customers may be unable to reach inference endpoints or send requests to the service. Engineering is actively working on recovery. We will...

2. resolved 2026-05-10 18:19 UTC

   Service has been fully restored. We have identified the root cause and are taking steps to prevent recurrence.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-08 20:04 UTC

   We're investigating failures when creating new projects. Existing workloads and resources remain fully operational. We will provide an update when more information is available.

2. investigating 2026-05-09 03:09 UTC

   The issue has been mitigated and project creation requests are completing successfully.

3. resolved 2026-05-09 03:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 22:19 UTC

   We are currently experiencing an issue with storage used disk capacity metrics in our Iceland (eu-iceland1) region. All data access, read/write operations, and service functionality continue to operate normally with no performance impact. Our team is actively working to restore...

2. resolved 2026-05-06 23:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: API, UI

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-05-04 22:26 UTC

   We are investigating an issue causing 503 errors when accessing the Crusoe Compute Console and API. Users may currently be unable to list instances or manage infrastructure resources. Our engineering team is actively working to identify the root cause. Further updates will be...

2. monitoring 2026-05-04 22:26 UTC

   The issues affecting the Crusoe Compute Console, API, and CLI have been fully resolved. Impact Window: The service interruption lasted from 2:42 PM PDT to 3:16 PM PDT. During this window, users may have experienced 503 errors and were unable to view or manage resources via the...

3. resolved 2026-05-04 23:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Persistent Storage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-17 01:30 UTC

   We are currently investigating an issue specifically affecting Persistent Volume (PVC) creation for Crusoe Managed Kubernetes (CMK) customers. While this interruption prevents the provisioning of new block storage volumes, it is strictly limited to block storage and does not...

2. resolved 2026-04-17 02:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: API, UI

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-01 13:29 UTC

   We are investigating an issue in our eu-iceland1 region that may be impacting the ability to manage resources. Our engineering team is actively working to identify the scope and cause. We will provide another update as more information becomes available.

2. monitoring 2026-04-01 13:51 UTC

   A fix has been implemented and we are monitoring the results. If you are experiencing issues, please contact Crusoe Support.

3. resolved 2026-04-01 14:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Crusoe Managed Kubernetes (CMK)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-30 21:12 UTC

   We are aware of an issue with an upstream dependency that may impact the ability to add new nodes to existing node pools. Existing clusters and running workloads are not affected. We are actively monitoring the situation and will provide updates as it progresses. If you are...

2. resolved 2026-03-30 23:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Crusoe Managed Kubernetes (CMK)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-18 20:21 UTC

   We are investigating an issue affecting Kubernetes CMK control plane operations. Customers may experience elevated latency or timeouts when retrieving cluster credentials via the CLI or console, and may be unable to create new clusters. Existing cluster workloads are not...

2. resolved 2026-03-18 23:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-04 19:36 UTC

   We are investigating an issue in our US-Southcentral region that may be impacting the ability to manage cluster resources via the API. Our engineering team is actively working to identify the scope and cause. We will provide another update as more information becomes available.

2. investigating 2026-03-04 21:25 UTC

   We are pleased to report that this incident is now resolved. We have confirmed that control plane functionality for all impacted clusters in the us-southcentral region has been fully restored. The issue was caused by network congestion on a small number of underlying physical...

3. resolved 2026-03-04 21:25 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-27 04:58 UTC

   We are currently investigating an issue impacting our Shared Disks in the eu-iceland1-a region. We are actively working with our storage vendor to resolve this issue. We will provide another update as soon as we have more information.

2. investigating 2026-02-27 04:58 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-02-27 05:36 UTC

   The issue has been mitigated and is now operating normally. We are monitoring the system to ensure continued stability.

4. resolved 2026-03-04 21:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-20 12:59 UTC

   We are currently investigating an issue impacting our Shared Disks in the eu-iceland1-a region. Customers may not be able to create, read, update, and delete operations. VM operations may also be impacted. We are working with our Storage vendor on a resolution currently.

2. resolved 2026-02-20 15:21 UTC

   A fix has been implemented which fixed the issue. All operations should have resumed normally.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-04 00:19 UTC

   We are currently investigating an issue affecting control plane operations for shared storage in the eu-iceland1-a region. Existing shared volumes and running VMs are not affected, but creation and deletion of shared volumes may be impacted. We are actively working with our...

2. monitoring 2026-02-04 00:50 UTC

   Our storage vendor has successfully mitigated the issue. Control plane operations are now fully operational. We will monitor for some time before declaring the issue resolved.

3. resolved 2026-02-04 05:07 UTC

   This issue has been resolved. If you are still experiencing any other issues related to this matter, please contact support@crusoe.ai.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 21:42 UTC

   We are currently investigating reports of failures when creating Custom Images in our EU-Iceland (eu-iceland1-a) region. Users may receive "Internal Server Errors" or experience operation timeouts when attempting to create Custom Images from existing disks. If you experience any...

2. resolved 2026-02-04 00:12 UTC

   This issue has been resolved. If you are still experiencing any other issues related to this matter, please contact support@crusoe.ai.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Container Registry

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-01 21:42 UTC

   Customers using CCR (Crusoe Container Registry ) will be unable to push or pull images in us-east1, eu-iceland1 and us-southcentral1. We are working on resolving this matter as soon as possible. If you experience any other issues, please reach out to support@crusoe.ai

2. resolved 2026-02-02 04:38 UTC

   This issue has been resolved. Please contact support@crusoe.ai if you are still experiencing any issues.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-29 09:28 UTC

   We are currently investigating an issue that is causing some Direct NFS mounts to be unavailable in the eu-iceland1 region. Customers utilizing Direct NFS for shared drives may be unable to access their mounts. We are actively diagnosing the problem. We will post another update...

2. investigating 2025-12-29 14:00 UTC

   It appears that several storage backend VIPs are experiencing connectivity problems. We are actively collaborating with both our networking vendor and our storage vendor to identify and implement a resolution.

3. monitoring 2025-12-29 22:29 UTC

   We have restored connectivity to all affected Direct NFS mounts by applying a mitigation to the network hardware. Service is now operating normally and we are monitoring the system to ensure continued stability.

4. resolved 2026-01-02 20:47 UTC

   This issue is resolved and connectivity to all Direct NFS mounts in the eu-iceland1 region has been fully restored. The network mitigation is verified, and the system is stable.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-16 18:19 UTC

   We are currently experiencing a network instability issue in eu-iceland1-a region, causing a subset of virtual machines to lose access to their boot disk. This is resulting in multiple VMs (Virtual Machines) throwing DNR (Device Not Ready) errors. We will provide another update...

2. resolved 2025-12-17 09:12 UTC

   A fix has been applied and the issue regarding "Device Not Ready" (DNR) errors in the eu-iceland1-a region is now resolved. All impacted services and Virtual Machines have returned to normal operations.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Shared Disks, eu-iceland1

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-16 17:13 UTC

   We are currently investigating slowness when using Shared Storage in eu-iceland1-a. We are working with our storage vendor to resolve the issue as soon as possible.

2. investigating 2025-12-16 17:36 UTC

   We are expanding the scope of impact for this incident. Customers will observe significant slowness and intermittent access issues when utilizing Shared Storage services in eu-iceland1-a region. We will provide another update as soon as we have further developments. Thank you...

3. investigating 2025-12-16 18:26 UTC

   We have implemented a fix for the storage performance issues in eu-iceland1-a. Storage latency and throughput have returned to normal operating levels. We are actively monitoring the service to ensure continued stability.

4. investigating 2025-12-16 18:53 UTC

   We are continuing to observe impact related to the storage performance degradation in eu-iceland1-a. Our engineering teams remain actively engaged with our vendor in focused remediation efforts and are working to address residual intermittent slowness for some customers...

5. investigating 2025-12-16 22:43 UTC

   Engineering teams are continuing to actively remediate specific storage metadata inconsistencies and stabilize network connectivity within the eu-iceland1-a region. During this window, customers may continue to experience intermittent write errors, latency spikes, or brief...

6. identified 2025-12-17 00:49 UTC

   Engineering teams are currently executing a targeted integrity verification process to permanently resolve the metadata inconsistencies reported earlier. To ensure strict data safety during this operation, the storage cluster has entered a protective maintenance state that...

7. monitoring 2025-12-17 02:05 UTC

   Engineering teams have completed the critical phase of the integrity verification process and have lifted the broad protective maintenance restrictions. As a result, service availability has been restored for the majority of volumes and data paths in the eu-iceland1-a region....

8. identified 2025-12-17 02:53 UTC

   Hello Team, during our monitoring we are observing VM operation failures, as well as shared volume create/update/delete failures due to ongoing impact to the storage control plane. Some customers may still observe issues when accessing existing volumes. A small subset of...

9. investigating 2025-12-17 21:22 UTC

   We are continuing to address the ongoing service instability affecting shared volumes in the eu-iceland1-a region. While engineering teams continue the previously reported background recovery efforts, we are observing intermittent performance fluctuations and connectivity drops,...

10. identified 2025-12-17 23:11 UTC

    Engineering teams have implemented configuration changes to isolate background recovery processes from active customer workloads. Following these adjustments, we are observing signs of stabilization in cluster performance and a reduction in the intermittent connectivity...

11. identified 2025-12-18 18:37 UTC

    The majority of customers should now observe a return to normal operations and consistent performance within the eu-iceland1-a region. While general cluster stability has been restored, engineering teams are continuing focused recovery efforts for a limited subset of customers...

12. identified 2025-12-18 23:00 UTC

    The storage cluster continues to operate with stable performance for the majority of workloads. Regarding the subset of volumes requiring further intervention, we are closely coordinating with our storage vendor to execute comprehensive integrity scans and fully map the scope of...

13. identified 2025-12-23 06:41 UTC

    To accelerate the VAST recovery progress at scale, we need to deploy an upgrade to the underlying VAST storage software. We are planning a maintenance window at 12:00 am PT on December 23rd. Target Start Time: 12:00 AM PST Expected Duration: 4 Hours Purpose: This VAST upgrade...

14. identified 2025-12-23 12:00 UTC

    The planned VAST storage software upgrade has been completed successfully across the cluster. We are now transitioning back to active recovery operations for the remaining volumes requiring remediation. With the new automated tooling now in place, engineering teams are resuming...

15. identified 2025-12-23 20:21 UTC

    We observed a blip that affected our storage cluster in the eu-iceland1-a region from 2025-12-23 19:52:53 UTC to 2025-12-23 20:03:47 UTC. This would have resulted in read, write, and update operations failing on all shared volumes. The service should be restored now. Our...

16. identified 2025-12-23 21:22 UTC

    We have completed our initial review of an approximately 10 minute storage outage in eu-iceland1-a region. The interruption was caused by a manual administrative error by our storage provider (VAST) during the data recovery process. While service was restored within minutes, we...

17. identified 2025-12-26 11:17 UTC

    We have identified a new storage network issue impacting accessibility of shared volumes in the eu-iceland1-a region. We are currently engaged with our storage partner, VAST, to remediate the issue and restore stable access. Further updates will be provided as we make progress.

18. identified 2025-12-26 14:39 UTC

    The storage network issues in the eu-iceland1-a region have been resolved, and access to shared volumes is restored. Together with our vendor VAST, we have stabilized the network layer and verified that I/O operations are performing normally. We will continue to monitor the...

19. identified 2025-12-26 22:54 UTC

    We have identified a new storage network issue impacting accessibility of shared volumes in the eu-iceland1-a region. We are currently engaged with our storage partner, VAST, to remediate the issue and restore stable access. Further updates will be provided as we make progress.

20. identified 2025-12-26 23:40 UTC

    We are expanding the scope of impact for the ongoing storage network issue in the eu-iceland1-a region. In addition to the accessibility of shared volumes, this issue is now also impacting Virtual Machine (VM) operations, including create, start, stop, and delete. We are...

21. identified 2025-12-27 03:45 UTC

    We have confirmed that the storage network issue in the eu-iceland1-a region is now resolved. The storage cluster is currently stable. Access to shared volumes should be restored for everyone, and all Virtual Machine (VM) operations—including create, start, stop, and delete—have...

22. identified 2025-12-27 17:23 UTC

    Our storage vendor will be applying a configuration update to the underlying storage nodes starting at 10:00 AM PT, which will take approximately 15 minutes to complete. This maintenance is designed to optimize and increase the speed of existing recovery workflows. We do not...

23. identified 2025-12-27 18:23 UTC

    The planned VAST configuration update has been completed successfully across the cluster. We are now transitioning back to active recovery operations for the remaining volumes requiring remediation. We will continue to monitor the progress and stability of the cluster as these...

24. identified 2025-12-28 01:03 UTC

    We are upgrading the VAST storage software at 6:00 AM PT on December 28th to further optimize recovery progress. This maintenance window is required to deploy critical improvements to the recovery process and has an expected duration of 4 hours. We do not anticipate any...

25. identified 2025-12-28 11:10 UTC

    We have identified an issue with the underlying storage infrastructure in the eu-iceland1-a region. Several storage components have gone offline unexpectedly, impacting the availability of shared volumes and preventing VMs management operations. We are working urgently with our...

26. identified 2025-12-28 13:48 UTC

    We have restored full service to the eu-iceland1-a storage cluster. The storage node failures have been remediated, and shared disks are once again performing normally. VMs operations have also been stabilized. We sincerely apologize for the continued disruption. Our teams are...

27. identified 2025-12-28 15:18 UTC

    To ensure the reliability of the system after today's issue, we are postponing the VAST storage software upgrade, initially planned at 6:00 AM PT on December 28th, to 9:00 AM PT. This maintenance window is required to deploy critical improvements to the recovery process and has...

28. identified 2025-12-28 21:53 UTC

    The planned VAST storage software upgrade, which began at 9:00 AM PT, has been completed successfully. The storage cluster is stable, and all services are operating normally.

29. identified 2025-12-30 19:23 UTC

    We are upgrading the VAST storage software at 12:00 PM PT today, December 30th, to optimize recovery progress further. This maintenance window is required to deploy critical improvements to the recovery process and has an expected duration of 4 hours. We do not anticipate any...

30. identified 2025-12-31 00:45 UTC

    The planned VAST storage software upgrade, which began at 12:00 PM PT, completed successfully. The storage cluster is stable, and all services are operating normally.

31. identified 2025-12-31 15:45 UTC

    We are performing an additional upgrade to the VAST storage software today, December 31st, at 9:00 AM PT, to further optimize and accelerate the recovery process. While we do not anticipate any downtime, you may experience temporary service degradation during this period. We...

32. identified 2025-12-31 20:53 UTC

    The planned VAST storage software upgrade, which began at 9:00 AM PT, completed successfully. The storage cluster is stable, and all services are operating normally.

33. identified 2026-01-01 17:01 UTC

    VAST is performing an additional upgrade to the storage software in our eu-iceland1-a region today, January 1st, at 10:00 AM PT. While we do not anticipate any downtime, you may experience temporary service degradation during this period. We appreciate your continued patience as...

34. identified 2026-01-02 18:06 UTC

    As of this morning, all planned activities to restore storage access have been completed. As we transition the system back to normal operations, we are now moving into a monitoring phase.

35. monitoring 2026-01-02 18:47 UTC

    As of this morning, all planned activities to restore storage access have been completed. As we transition the system back to normal operations, we are now moving into a monitoring phase.

36. resolved 2026-01-07 17:25 UTC

    Final monitoring of the eu-iceland1-a storage cluster has been successfully completed, and all services remain stable. All planned recovery activities and software upgrades are finished, with performance and VM operations restored to normal levels. This incident is now resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: API, UI

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-18 12:48 UTC

   We are currently investigating an issue affecting access to the Cloud Console UI and API. Users may be unable to log in to our cloud services or access the management dashboard.

2. investigating 2025-11-18 14:28 UTC

   We are continuing to investigate this issue.

3. investigating 2025-11-18 14:28 UTC

   We are continuing to investigate this issue.

4. investigating 2025-11-18 16:37 UTC

   The issue is resolved and Cloud Console is accessible and functioning as expected.

5. resolved 2025-11-18 16:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Datacenter Networking

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-30 00:46 UTC

   We are currently investigating an incident affecting VM connectivity and performance in the Iceland region. Our Engineering teams are actively engaged and working to isolate the root cause. We will provide updates as our investigation progresses.

2. investigating 2025-10-30 02:35 UTC

   We have isolated the issue to a subset of VMs within the Iceland region and determined that it is not a core network transport failure. Our Engineering teams are continuing to actively troubleshoot the issue to restore service as soon as possible.

3. investigating 2025-10-30 02:36 UTC

   We are continuing to investigate this issue.

4. identified 2025-10-30 04:55 UTC

   We have identified the issue and are deploying a fix.

5. monitoring 2025-10-30 06:10 UTC

   We have mitigated the issue and connectivity is confirmed to be restored. We will monitor overnight.

6. resolved 2025-11-04 19:46 UTC

   Issue resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1, us-northcentral1, us-southcentral1, eu-iceland1

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-09 21:37 UTC

   We have identified an issue that is preventing new or restarted Virtual Machines from booting successfully. Existing, currently running VMs are operational. We advise customers to avoid rebooting critical workloads until a resolution is in place. Our engineering teams are...

2. investigating 2025-10-09 21:38 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-10 01:59 UTC

   We have determined that the problem is sporadic and limited to a specific subset of our host nodes. Existing, currently running VMs are operational. We still strongly recommend customers avoid rebooting critical workloads until the permanent fix is confirmed to be fully...

4. investigating 2025-10-10 02:02 UTC

   We are continuing to investigate this issue.

5. investigating 2025-10-14 23:42 UTC

   We are continuing to investigate this issue.

6. resolved 2025-10-14 23:43 UTC

   Update: The issue is now resolved. The engineering team has implemented a fix and confirmed that normal provisioning operations have been restored.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-southcentral1, eu-iceland1

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-03 01:10 UTC

   We have identified an issue that is preventing new or restarted Virtual Machines from booting successfully on all instance types. Existing, currently running VMs are not affected and will continue to operate normally. We advise customers to avoid rebooting critical workloads on...

2. resolved 2025-10-03 07:09 UTC

   Update: The issue is now resolved. The engineering team has implemented a fix and confirmed that normal provisioning operations have been restored.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-02 04:00 UTC

   We have identified an issue that is preventing new or restarted Virtual Machines from booting successfully on our A100 Infiniband hardware fleet. Any new VM provisioning request for this hardware type will also fail. Additionally, any existing VM on an A100 Infiniband node that...

2. monitoring 2025-10-02 20:20 UTC

   A fix has been implemented, and we are monitoring the environment.

3. resolved 2025-10-02 20:50 UTC

   This incident is now resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: eu-iceland1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-30 18:45 UTC

   We are currently investigating an issue impacting virtual machine accessibility in eu-iceland1-a region. Some users may be unable to access their VMs at this time. We appreciate your patience and will provide updates as more information becomes available.

2. investigating 2025-09-30 19:48 UTC

   We're making significant progress in resolving the virtual machine accessibility issues in the eu-iceland1-a region. We apologize for the continued disruption and thank you for your patience as we work to restore full service. We will provide another update as soon as more...

3. identified 2025-09-30 20:34 UTC

   We have identified and mitigated the issue. Although no further impact is expected, we are continuing to monitor. If you are still experiencing issues, please reach out to us through support@crusoecloud.com and we will investigate further.

4. monitoring 2025-09-30 21:55 UTC

   A fix has been applied and the outage has been mitigated. Services have returned to normal operations in eu-iceland1-a region. We are continuing to monitor. Please contact support@crusoecloud.com if you are still experiencing any issues.

5. resolved 2025-10-01 00:00 UTC

   This incident has been resolved. Please contact support@crusoe.ai if you are still experiencing any issues.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-southcentral1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-30 10:22 UTC

   We are currently investigating an issue with machine accessibility and performance issues in the us-southcentral1 region . Some users may be unable to access their VMs at this time or see performance degradation. We appreciate your patience and will provide updates as more...

2. resolved 2025-09-30 10:49 UTC

   A fix has been implemented. This incident is now resolved

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: UI, Crusoe Managed Kubernetes (CMK)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-19 21:53 UTC

   Please be aware that the user interface is currently not showing the correct capacity for CMK nodepool creation, even when quota is available. This is a UI-specific bug. As a temporary workaround, please use the command-line interface (CLI) to successfully create nodepools. Our...

2. resolved 2025-09-20 01:14 UTC

   The fix has been deployed, and the user interface now correctly displays the capacity for CMK nodepool creation. You can now use either the UI or the CLI to provision new nodepools.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-southcentral1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-19 07:33 UTC

   We are currently investigating an issue impacting the ability to start Virtual Machines (VMs) in our us-southcentral1-a region. Our engineering team has identified a potential issue and is actively working on a resolution. Thank you for your patience as we work to restore full...

2. resolved 2025-09-19 13:20 UTC

   A fix has been implemented. This incident is now resolved

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1, Infiniband Networks

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-20 17:09 UTC

   We're investigating a service degradation in our us-east1-a region, triggered by a facility power disruption at our data center. The primary impact is to the Infiniband networking fabric, which may cause intermittent errors or failures for multi-node, distributed workloads. Some...

2. investigating 2025-08-21 02:32 UTC

   We are continuing to investigate and mitigate the service degradation affecting our us-east1-a region, following a facility power disruption at our data center. Our teams remain in close coordination with the data center provider as they work to fully restore services. Recovery...

3. monitoring 2025-08-21 19:59 UTC

   We have successfully mitigated the issue affecting the us-east1-a region. The facility power disruption has been addressed, and the impacted Infiniband networking fabric and associated systems have returned to normal operation. All affected services are now stable, and full...

4. resolved 2025-08-21 23:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-01 03:18 UTC

   We have identified an issue that is preventing new or restarted Virtual Machines from booting successfully on our A100 Infiniband hardware fleet. Any new VM provisioning request for this hardware type will also fail. Additionally, any existing VM on an A100 Infiniband node that...

2. identified 2025-08-01 03:44 UTC

   The issue has been identified, and we have tested a fix internally. We are working on rolling out the fix to our A100 Infiniband type servers now.

3. monitoring 2025-08-01 05:06 UTC

   A fix has been implemented, and we are monitoring the environment for now.

4. resolved 2025-08-01 06:21 UTC

   This incident is now resolved

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Persistent Storage

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-24 08:30 UTC

   We are currently investigating an issue affecting VM's in eu-iceland1

2. identified 2025-07-24 10:26 UTC

   We have identified an issue with our persistent disk storage system for a subset of VM's in eu-iceland1. Our engineers are now working to restore service.

3. monitoring 2025-07-24 10:52 UTC

   A fix has been implemented for the persistent disk storage system. We are observing recovery, and affected virtual machines in eu-iceland1 are returning to a healthy state. Our team will continue to monitor the platform to ensure full service restoration and stability. We will...

4. resolved 2025-07-24 11:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: API

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-11 14:28 UTC

   We're currently investigating an issue impacting our control plane in the US-Southcentral region. Customers may experience errors or timeouts when making certain API calls, including those for creating new virtual machines. Our engineering team is investigating the underlying...

2. identified 2025-07-11 15:11 UTC

   We've identified a potential issue on the control plane network and we're working to address the issue currently.

3. monitoring 2025-07-11 15:32 UTC

   A fix has been applied and the outage has been mitigated. Services have returned to normal operations in US-Southcentral region. We are continuing to monitor the situation and validate preventive measures. Please contact support@crusoecloud.com if you are still experiencing any...

4. resolved 2025-07-11 16:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: Persistent Storage

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-30 18:05 UTC

   We are currently investigating a potential service interruption that may impact VMs to be unreachable in the us-northcentral1-a region. If you are experiencing issues in this region, please reach out to support@crusoecloud.com

2. investigating 2025-06-30 22:01 UTC

   Our teams are working diligently and believe we have identified the root cause and we are working on implementing a resolution. We will continue to provide updates on this page as further developments occur.

3. investigating 2025-07-01 01:34 UTC

   We are continuing our in-depth investigation into the intermittent storage connectivity issues impacting VM reachability in the us-northcentral1-a region. We will provide more information as it becomes available.

4. investigating 2025-07-01 05:21 UTC

   Our team is continuing its in-depth investigation into the intermittent storage connectivity issues impacting VM reachability in the us-northcentral1-a region, in collaboration with our vendor. We will keep you posted on further developments

5. investigating 2025-07-01 10:06 UTC

   We are continuing our dedicated investigation into the intermittent storage connectivity issues impacting VM reachability in us-northcentral1-a. Our teams are working in close collaboration with our storage vendor to analyze the underlying cause. We recognize the impact this is...

6. investigating 2025-07-01 14:14 UTC

   We are seeing signs of recovery, and some previously impacted VMs in the us-northcentral1-a region are now available. Our teams are closely monitoring the environment and continuing their work with our vendor to restore full service for all remaining affected instances.

7. monitoring 2025-07-01 20:57 UTC

   A fix has been applied and the outage has been mitigated. Services have returned to normal operations in us-northcentral1-a region. We are continuing to monitor the situation and validate preventive measures. Please contact support@crusoecloud.com if you are still experiencing...

8. resolved 2025-07-02 17:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: API, UI, us-east1, us-northcentral1, us-southcentral1, eu-iceland1

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-06-12 19:55 UTC

   We are currently experiencing an outage with our 3rd party service provider, which is intermittently impacting the ability to provision and manage Virtual Machines (VMs) across all of our regions.

2. investigating 2025-06-12 20:03 UTC

   We are continuing to investigate this issue.

3. investigating 2025-06-12 20:06 UTC

   We are continuing to investigate this issue.

4. investigating 2025-06-12 20:16 UTC

   We are expanding the scope of this incident to include the Crusoe console being inaccessible. This means that users are currently unable to log in, view, or manage resources through the Crusoe console interface. We are investigating this alongside the existing issues.

5. monitoring 2025-06-12 21:08 UTC

   We're starting to see signs of recovery across affected services, and our team is monitoring the situation very closely.

6. resolved 2025-06-12 21:35 UTC

   All Crusoe Cloud services have been restored and are fully operational. We will continue to monitor our platform. If you notice any issues please reach out to support@crusoecloud.com

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-11 03:10 UTC

   We are currently investigating an issue impacting virtual machine accessibility. Some users may be unable to stop and start Virtual Machines.

2. monitoring 2025-06-11 03:20 UTC

   We have identified the issue and a fix has been implemented. Currently, there is no further impact expected to virtual machine accessibility. We are currently monitoring the environment.

3. resolved 2025-06-11 03:36 UTC

   We are marking this incident as resolved. Please reach out to support@crusoecloud.com if you experience any issues.

Excerpts are shortened. Read the full incident on Crusoe's status page.

Affected: us-east1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-30 13:05 UTC

   We are currently investigating a potential service interruption that may impact some customers in our us-east1-a region. If you are experiencing issues in this region, please reach out to support@crusoecloud.com

2. investigating 2025-05-30 13:18 UTC

   We are continuing to investigate this issue.

3. investigating 2025-05-30 13:32 UTC

   We are currently investigating an issue impacting virtual machine accessibility in us-east1-a region. Some users may be unable to access their VMs at this time. We appreciate your patience and will provide updates as more information becomes available.

4. investigating 2025-05-30 13:33 UTC

   We are continuing to investigate this issue.

5. investigating 2025-05-30 13:34 UTC

   We are continuing to investigate this issue.

6. investigating 2025-05-30 13:44 UTC

   We are continuing to investigate this issue.

7. investigating 2025-05-30 15:24 UTC

   We're making significant progress in resolving the virtual machine accessibility issues in the us-east1-a region. We apologize for the continued disruption and thank you for your patience as we work to restore full service. We will provide another update as soon as more...

8. monitoring 2025-05-30 15:55 UTC

   We have identified and mitigated the underlying cause. Although no further impact is expected, we are continuing to monitor. If you are still experiencing issues, please reach out to us through support@crusoecloud.com and we will investigate further.

9. monitoring 2025-05-30 15:55 UTC

   We are continuing to monitor for any further issues.

10. monitoring 2025-05-30 16:45 UTC

    A fix has been applied and the outage has been mitigated. Services have returned to normal operations in us-east1-a region. We are continuing to monitor the situation and validate preventive measures. Please contact support@crusoecloud.com if you are still experiencing any...

11. resolved 2025-05-30 16:52 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Crusoe's status page.