- Detected by Pingoru
- May 25, 2026, 12:32 PM UTC
- Resolved
- May 26, 2026, 12:26 AM UTC
- Duration
- 11h 54m
Affected: Shared Diskseu-iceland1
Timeline · 5 updates
-
investigating May 25, 2026, 12:32 PM 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.
-
investigating May 25, 2026, 01:08 PM UTC
We are continuing to investigate this issue.
-
investigating May 25, 2026, 02:28 PM UTC
We are continuing to investigate this issue.
-
identified May 25, 2026, 03:15 PM 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.
-
resolved May 26, 2026, 12:26 AM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 01:37 AM UTC
- Resolved
- May 20, 2026, 09:09 PM UTC
- Duration
- 19h 32m
Affected: us-east1Container RegistryVPC Networking
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 08:24 AM UTC
- Resolved
- May 19, 2026, 01:19 AM UTC
- Duration
- 16h 55m
Affected: us-southcentral1eu-iceland1
Timeline · 4 updates
-
identified May 18, 2026, 08:24 AM 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 recovery. We will provide an update when more information is available.
-
identified May 18, 2026, 11:27 AM 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 continues. Existing running workloads and resources remain fully operational and are not impacted. We will provide a further update as soon as more information becomes available.
-
monitoring May 18, 2026, 02:34 PM 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 continue to monitor both regions closely and are working on a permanent fix to prevent recurrence. We apologize for any inconvenience this may have caused.
-
resolved May 19, 2026, 01:19 AM 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 running workloads and resources remained fully operational throughout the incident. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 09:34 PM UTC
- Resolved
- May 14, 2026, 12:09 AM UTC
- Duration
- 2h 34m
Affected: Container Registry
Timeline · 2 updates
-
investigating May 13, 2026, 09:34 PM 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 [email protected]
-
resolved May 14, 2026, 12:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 10, 2026, 02:41 PM UTC
- Resolved
- May 10, 2026, 06:19 PM UTC
- Duration
- 3h 38m
Timeline · 2 updates
-
investigating May 10, 2026, 02:41 PM 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 provide an update when more information is available.
-
resolved May 10, 2026, 06:19 PM UTC
Service has been fully restored. We have identified the root cause and are taking steps to prevent recurrence.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 08:04 PM UTC
- Resolved
- May 09, 2026, 03:09 AM UTC
- Duration
- 7h 4m
Affected: API
Timeline · 3 updates
-
investigating May 08, 2026, 08:04 PM 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.
-
investigating May 09, 2026, 03:09 AM UTC
The issue has been mitigated and project creation requests are completing successfully.
-
resolved May 09, 2026, 03:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 10:19 PM UTC
- Resolved
- May 06, 2026, 11:41 PM UTC
- Duration
- 1h 21m
Affected: Shared Disks
Timeline · 2 updates
-
investigating May 06, 2026, 10:19 PM 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 capacity metrics. We will provide updates as restoration progresses.
-
resolved May 06, 2026, 11:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 04, 2026, 10:26 PM UTC
- Resolved
- May 04, 2026, 11:29 PM UTC
- Duration
- 1h 3m
Affected: APIUI
Timeline · 3 updates
-
monitoring May 04, 2026, 10:26 PM 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 provided as soon as they are available.
-
monitoring May 04, 2026, 10:26 PM 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 web console, CLI, or API. Our engineering team identified the issue and implemented a fix to restore all management services. We have verified that all systems are now performing as expected. We are continuing to monitor the platform and will implement additional safeguards and alerting to improve our response and stability moving forward. Note: Active customer workloads and existing infrastructure remained operational and were not impacted by this management-layer interruption.
-
resolved May 04, 2026, 11:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 01:30 AM UTC
- Resolved
- Apr 17, 2026, 02:52 AM UTC
- Duration
- 1h 21m
Affected: Persistent Storage
Timeline · 2 updates
-
investigating Apr 17, 2026, 01:30 AM 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 impact Shared Disks or other services. Existing volumes and active workloads remain fully operational and unaffected. Our engineering team has identified the root cause and is restoring the service. We expect to provide a final update once provisioning functionality is fully restored.
-
resolved Apr 17, 2026, 02:52 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 01:29 PM UTC
- Resolved
- Apr 01, 2026, 02:05 PM UTC
- Duration
- 35m
Affected: APIUI
Timeline · 3 updates
-
investigating Apr 01, 2026, 01:29 PM 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.
-
monitoring Apr 01, 2026, 01:51 PM UTC
A fix has been implemented and we are monitoring the results. If you are experiencing issues, please contact Crusoe Support.
-
resolved Apr 01, 2026, 02:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 30, 2026, 09:12 PM UTC
- Resolved
- Mar 30, 2026, 11:14 PM UTC
- Duration
- 2h 2m
Affected: Crusoe Managed Kubernetes (CMK)
Timeline · 2 updates
-
investigating Mar 30, 2026, 09:12 PM 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 experiencing issues, please contact Crusoe Support.
-
resolved Mar 30, 2026, 11:14 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 18, 2026, 08:21 PM UTC
- Resolved
- Mar 18, 2026, 11:30 PM UTC
- Duration
- 3h 8m
Affected: Crusoe Managed Kubernetes (CMK)
Timeline · 2 updates
-
investigating Mar 18, 2026, 08:21 PM 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 affected. We will provide a further update as our investigation continues.
-
resolved Mar 18, 2026, 11:30 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 04, 2026, 07:36 PM UTC
- Resolved
- Mar 04, 2026, 09:25 PM UTC
- Duration
- 1h 49m
Affected: API
Timeline · 3 updates
-
investigating Mar 04, 2026, 07:36 PM 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.
-
investigating Mar 04, 2026, 09:25 PM 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 hosts. This has been remediated by isolating the source of the traffic. We will be conducting a full post-mortem to prevent a recurrence and apologize for any disruption this incident caused.
-
resolved Mar 04, 2026, 09:25 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2026, 04:58 AM UTC
- Resolved
- Mar 04, 2026, 09:05 PM UTC
- Duration
- 5d 16h
Affected: Shared Disks
Timeline · 4 updates
-
investigating Feb 27, 2026, 04:58 AM 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.
-
investigating Feb 27, 2026, 04:58 AM UTC
We are continuing to investigate this issue.
-
monitoring Feb 27, 2026, 05:36 AM UTC
The issue has been mitigated and is now operating normally. We are monitoring the system to ensure continued stability.
-
resolved Mar 04, 2026, 09:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 12:59 PM UTC
- Resolved
- Feb 20, 2026, 03:21 PM UTC
- Duration
- 2h 22m
Affected: Shared Disks
Timeline · 2 updates
-
investigating Feb 20, 2026, 12:59 PM 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.
-
resolved Feb 20, 2026, 03:21 PM UTC
A fix has been implemented which fixed the issue. All operations should have resumed normally.
Read the full incident report →
- Detected by Pingoru
- Feb 04, 2026, 12:19 AM UTC
- Resolved
- Feb 04, 2026, 05:07 AM UTC
- Duration
- 4h 47m
Affected: Shared Disks
Timeline · 3 updates
-
investigating Feb 04, 2026, 12:19 AM 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 storage vendor to resolve this issue. We will provide another as soon as we have more information.
-
monitoring Feb 04, 2026, 12:50 AM 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.
-
resolved Feb 04, 2026, 05:07 AM UTC
This issue has been resolved. If you are still experiencing any other issues related to this matter, please contact [email protected].
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 09:42 PM UTC
- Resolved
- Feb 04, 2026, 12:12 AM UTC
- Duration
- 2h 29m
Timeline · 2 updates
-
investigating Feb 03, 2026, 09:42 PM 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 other issues, please reach out to [email protected].
-
resolved Feb 04, 2026, 12:12 AM UTC
This issue has been resolved. If you are still experiencing any other issues related to this matter, please contact [email protected].
Read the full incident report →
- Detected by Pingoru
- Feb 01, 2026, 09:42 PM UTC
- Resolved
- Feb 02, 2026, 04:38 AM UTC
- Duration
- 6h 56m
Affected: Container Registry
Timeline · 2 updates
-
investigating Feb 01, 2026, 09:42 PM 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 [email protected]
-
resolved Feb 02, 2026, 04:38 AM UTC
This issue has been resolved. Please contact [email protected] if you are still experiencing any issues.
Read the full incident report →
- Detected by Pingoru
- Dec 29, 2025, 09:28 AM UTC
- Resolved
- Jan 02, 2026, 08:47 PM UTC
- Duration
- 4d 11h
Affected: Shared Disks
Timeline · 4 updates
-
investigating Dec 29, 2025, 09:28 AM 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 as soon as more information is available.
-
investigating Dec 29, 2025, 02:00 PM 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.
-
monitoring Dec 29, 2025, 10:29 PM 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.
-
resolved Jan 02, 2026, 08:47 PM 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.
Read the full incident report →
- Detected by Pingoru
- Dec 26, 2025, 02:39 PM UTC
- Resolved
- Jan 07, 2026, 05:25 PM UTC
- Duration
- 12d 2h
Affected: Shared Diskseu-iceland1
Timeline · 36 updates
Read the full incident report →
- Detected by Pingoru
- Dec 16, 2025, 06:19 PM UTC
- Resolved
- Dec 17, 2025, 09:12 AM UTC
- Duration
- 14h 53m
Affected: Shared Disks
Timeline · 2 updates
-
investigating Dec 16, 2025, 06:19 PM 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 as soon as we have further developments. Thank you for your patience as we work to restore full service as quickly as possible.
-
resolved Dec 17, 2025, 09:12 AM 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.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:48 PM UTC
- Resolved
- Nov 18, 2025, 04:38 PM UTC
- Duration
- 3h 50m
Affected: APIUI
Timeline · 5 updates
-
investigating Nov 18, 2025, 12:48 PM 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.
-
investigating Nov 18, 2025, 02:28 PM UTC
We are continuing to investigate this issue.
-
investigating Nov 18, 2025, 02:28 PM UTC
We are continuing to investigate this issue.
-
investigating Nov 18, 2025, 04:37 PM UTC
The issue is resolved and Cloud Console is accessible and functioning as expected.
-
resolved Nov 18, 2025, 04:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 30, 2025, 12:46 AM UTC
- Resolved
- Nov 04, 2025, 07:46 PM UTC
- Duration
- 5d 19h
Affected: Datacenter Networking
Timeline · 6 updates
-
investigating Oct 30, 2025, 12:46 AM 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.
-
investigating Oct 30, 2025, 02:35 AM 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.
-
investigating Oct 30, 2025, 02:36 AM UTC
We are continuing to investigate this issue.
-
identified Oct 30, 2025, 04:55 AM UTC
We have identified the issue and are deploying a fix.
-
monitoring Oct 30, 2025, 06:10 AM UTC
We have mitigated the issue and connectivity is confirmed to be restored. We will monitor overnight.
-
resolved Nov 04, 2025, 07:46 PM UTC
Issue resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 09:37 PM UTC
- Resolved
- Oct 14, 2025, 11:43 PM UTC
- Duration
- 5d 2h
Affected: us-east1us-northcentral1us-southcentral1eu-iceland1
Timeline · 6 updates
-
investigating Oct 09, 2025, 09:37 PM 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 actively investigating the root cause and are working to restore normal provisioning operations as quickly as possible.
-
investigating Oct 09, 2025, 09:38 PM UTC
We are continuing to investigate this issue.
-
investigating Oct 10, 2025, 01:59 AM 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 deployed. If you are currently experiencing issues with starting or restarting VMs, please open a support ticket so we can immediately address your specific host. We will provide another update once the targeted fix has been deployed to the identified hosts and we have confirmed stability.
-
investigating Oct 10, 2025, 02:02 AM UTC
We are continuing to investigate this issue.
-
investigating Oct 14, 2025, 11:42 PM UTC
We are continuing to investigate this issue.
-
resolved Oct 14, 2025, 11:43 PM UTC
Update: The issue is now resolved. The engineering team has implemented a fix and confirmed that normal provisioning operations have been restored.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 04:00 AM UTC
- Resolved
- Oct 02, 2025, 08:50 PM UTC
- Duration
- 16h 49m
Affected: us-east1
Timeline · 3 updates
-
identified Oct 02, 2025, 04:00 AM 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 is stopped and started (or rebooted) will also fail to come back online. Existing, currently running VMs are not affected and will continue to operate normally. We advise customers to avoid rebooting critical workloads on this hardware until a resolution is in place. Our engineering teams are actively investigating the root cause and are working to restore normal provisioning operations as quickly as possible.
-
monitoring Oct 02, 2025, 08:20 PM UTC
A fix has been implemented, and we are monitoring the environment.
-
resolved Oct 02, 2025, 08:50 PM UTC
This incident is now resolved.
Read the full incident report →