Crusoe: Control Plane Service Outage
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
Crusoe’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +2 h vs the first vendor naming Google Cloud)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>29 vendors, 28 blamed Google Cloud<br/>Pinecone, Northflank, imgix +26"]:::blames
root --> h1
h4["1 to 4 hours later<br/>12 vendors, 11 blamed Google Cloud<br/>Smartsheet, Daily, Confluent +9"]:::blames
root --> h4
later["Later<br/>1 vendor, 1 blamed Google Cloud<br/>Zilliz"]:::blames
root --> later
p0["Firebase<br/>own incident not archived"]:::inferred
root -.-> p0
k0["Codeium, Windsurf<br/>+13 min"]:::hop2
p0 -->|"blamed Firebase"| k0
p1["Anthropic<br/>posted +28 min, did not name Google Cloud"]:::timing
root -.-> p1
k1["GitHub, GitHub Copilot<br/>+24 min"]:::hop2
p1 -->|"blamed Anthropic"| k1
p2["Cloudflare<br/>own incident not archived"]:::inferred
root -.-> p2
k2["Doppler, Jupyter (Anaconda), Socket +4<br/>+35 min to +3 h 41 min"]:::hop2
p2 -->|"blamed Cloudflare"| k2
me["Crusoe (this incident)<br/>posted +2 h"]:::me
root -.->|"same window"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Affected components: GPU Virtual Machines - us-northcentral1us-northcentral1GPU Virtual Machines - us-southcentral1us-southcentral1GPU Virtual Machines - us-east1us-east1UIAPIeu-iceland1GPU Virtual Machines - eu-iceland1
Timeline of updates
- investigating
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.
- investigating
We are continuing to investigate this issue.
- investigating
We are continuing to investigate this issue.
- investigating
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.
- monitoring
We're starting to see signs of recovery across affected services, and our team is monitoring the situation very closely.
- resolved
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
Changes Rewindex caught on this incident
- Jun 12, 2025Major incident: Control Plane Service Outage
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).