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 issues.
Posted May 30, 2025 - 16:45 UTC
Update
We are continuing to monitor for any further issues.
Posted May 30, 2025 - 15:55 UTC
Monitoring
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.
Posted May 30, 2025 - 15:55 UTC
Update
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 information is available or when services are fully restored. You can continue to contact our support team at support@crusoecloud.com, if there are any other concerns to address
Posted May 30, 2025 - 15:24 UTC
Update
We are continuing to investigate this issue.
Posted May 30, 2025 - 13:44 UTC
Update
We are continuing to investigate this issue.
Posted May 30, 2025 - 13:34 UTC
Update
We are continuing to investigate this issue.
Posted May 30, 2025 - 13:33 UTC
Update
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.
Posted May 30, 2025 - 13:32 UTC
Update
We are continuing to investigate this issue.
Posted May 30, 2025 - 13:18 UTC
Investigating
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
Posted May 30, 2025 - 13:05 UTC
This incident affected: GPU Virtual Machines (us-east1).