Is Crusoe down?

Last checked 3m ago
Current status
Crusoe is up

No incidents right now.

Official status page: https://status.crusoecloud.com · Polled every 5 minutes · 15 components tracked

Crusoe is operational right now. Last checked 3m ago; the most recent incident resolved 2d ago.

Real-time Crusoe status, recent outages, and incident history — pulled directly from Crusoe's official status page at https://status.crusoecloud.com every 5 minutes. Pingoru tracks 15 Crusoe services and has captured 25 incidents in the last 90 days (97.85% uptime). Get email, Slack, Discord, or webhook alerts the moment Crusoe reports a new incident — free for 5 monitors, no credit card.

Users who monitor Crusoe also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Crusoe uptime 97.85% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 56m
    Started Jun 11, 2026, 04:50 PM UTC · Resolved Jun 11, 2026, 07:47 PM UTC
    us-east1us-southcentral1eu-iceland1
    Timeline · 3 updates
    • investigating · Jun 11, 2026, 04:50 PM 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.

    • identified · Jun 11, 2026, 04:51 PM UTC

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

    • resolved · Jun 11, 2026, 07:47 PM UTC

      This issue is now resolved.

    Latest: This issue is now resolved.

  2. Resolved 16h 43m
    Started Jun 08, 2026, 10:12 PM UTC · Resolved Jun 09, 2026, 02:56 PM UTC
    Wide Area Networking (WAN)VPC NetworkingDatacenter Networking
    Timeline · 3 updates
    • investigating · Jun 08, 2026, 10:12 PM 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

    • monitoring · Jun 08, 2026, 11:41 PM 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.

    • resolved · Jun 09, 2026, 02:56 PM UTC

      This issue has been resolved.

    Latest: This issue has been resolved.

  3. Resolved 2h 16m
    Started Jun 04, 2026, 02:10 AM UTC · Resolved Jun 04, 2026, 04:27 AM UTC
    VPC Networking
    Timeline · 3 updates
    • investigating · Jun 04, 2026, 02:10 AM 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

    • monitoring · Jun 04, 2026, 03:31 AM UTC

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

    • resolved · Jun 04, 2026, 04:27 AM UTC

      This issue is now resolved.

    Latest: This issue is now resolved.

  4. Resolved 11h 54m
    Started May 25, 2026, 12:32 PM UTC · Resolved May 26, 2026, 12:26 AM UTC
    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.

    Latest: This issue has been resolved.

  5. Resolved 19h 32m
    Started May 20, 2026, 01:37 AM UTC · Resolved May 20, 2026, 09:09 PM UTC
    us-east1Container RegistryVPC Networking
    Timeline · 15 updates
    • investigating · May 20, 2026, 01:37 AM 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 as Not Ready. Engineering is engaged and actively working to identify the cause and restore service. We will provide updates as we have more information.

    • investigating · May 20, 2026, 03:51 AM UTC

      We are continuing to investigate this issue.

    • identified · May 20, 2026, 06:19 AM 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 will continue to provide updates as remediation progresses.

    • identified · May 20, 2026, 08:25 AM 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 remains impacted at this time. We will provide further updates as progress continues.

    • identified · May 20, 2026, 09:28 AM 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 will provide further updates as recovery continues.

    • identified · May 20, 2026, 10:32 AM 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.

    • identified · May 20, 2026, 11:28 AM 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

    • identified · May 20, 2026, 12:37 PM 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.

    • identified · May 20, 2026, 01:27 PM 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 advances.

    • identified · May 20, 2026, 02:27 PM 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.

    • identified · May 20, 2026, 03:35 PM 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.

    • identified · May 20, 2026, 04:30 PM 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.

    • identified · May 20, 2026, 05:55 PM 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.

    • identified · May 20, 2026, 06:55 PM 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.

    • resolved · May 20, 2026, 09:09 PM UTC

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

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

See the full Crusoe outage history

10 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Crusoe outage history →

Or sign up free to get alerts when Crusoe breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 15 incidents View full outage history →