Is Crusoe down?
Last checked just nowNo incidents right now.
Crusoe is operational right now. Last checked just now; the most recent incident resolved 6d 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 19 Crusoe services and has captured 18 incidents in the last 90 days (99.65% uptime). Get email, Slack, Discord, or webhook alerts the moment Crusoe reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- us-east2
Timeline · 3 updates
- identified · Sep 09, 2026, 09:56 AM 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. We will provide more information as soon as it becomes available.
- monitoring · Sep 09, 2026, 10:51 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Sep 09, 2026, 11:19 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Sep 03, 2026, 02:24 PM UTC
We identified general network errors affecting service connectivity in our us-east2 region. The issue has been resolved and services are operating normally.
Latest: We identified general network errors affecting service connectivity in our us-east2 region. The issue has been resolved and services are operating normally.
-
-
Timeline · 6 updates
- investigating · Sep 02, 2026, 08:22 AM UTC
We are investigating "insufficient capacity" errors when creating VMs or 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.
- investigating · Sep 02, 2026, 09:44 AM UTC
We continue investigating "insufficient capacity" errors when creating VMs or 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.
- investigating · Sep 02, 2026, 11:07 AM UTC
We continue investigating "insufficient capacity" errors when creating VMs or CMK clusters in us-east2 region. We'll share an update as soon as we have more information available.
- investigating · Sep 02, 2026, 12:56 PM 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.
- monitoring · Sep 02, 2026, 01:40 PM 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.
- resolved · Sep 02, 2026, 03:57 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Datacenter Networking
Timeline · 4 updates
- investigating · Jul 09, 2026, 02:45 PM 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 working to mitigate the issue as soon as possible. We will provide further updates as more information becomes available.
- investigating · Jul 09, 2026, 03:10 PM 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 resolution. We apologize for any disruption this has caused.
- monitoring · Jul 09, 2026, 03:12 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Jul 09, 2026, 04:58 PM 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.
Latest: 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 yo…
-
- Container Registry
Timeline · 4 updates
- investigating · Jul 08, 2026, 05:23 AM 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 authentication errors. Our engineering team is actively investigating. We will provide more information as we investigate the issue.
- investigating · Jul 08, 2026, 11:03 AM 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.
- monitoring · Jul 08, 2026, 09:57 PM 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.
- resolved · Jul 09, 2026, 03:23 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Crusoe outage history
1 more incident 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
- Started Sep 09, 2026, 09:56 AM UTC · Resolved Sep 09, 2026, 11:19 AM UTC · 1h 22m
- Started Sep 03, 2026, 12:30 PM UTC · Resolved Sep 03, 2026, 12:30 PM UTC · —
- Started Sep 02, 2026, 08:22 AM UTC · Resolved Sep 02, 2026, 03:57 PM UTC · 7h 35m
- Started Jul 09, 2026, 02:45 PM UTC · Resolved Jul 09, 2026, 04:58 PM UTC · 2h 12m
- Crusoe Container Registry (CCR) Outage – TLS/Auth Errors in US South Central(us-southcentral1-a) ResolvedStarted Jul 08, 2026, 05:23 AM UTC · Resolved Jul 09, 2026, 03:23 PM UTC · 1d 10h
- Started Jun 25, 2026, 11:33 PM UTC · Resolved Jun 25, 2026, 09:30 AM UTC · —