Facility issue in us-east2-a
This incident has been resolved.
The latest update from Crusoe.
State
Resolved
Started
17 d ago
2026-10-15 13:12 UTC
Lasted
3 days
until 2026-10-18 20:22 UTC
Worst impact
Major outage
Timeline
10 updatesInvestigating
2 h 52 min 4%
Identified
3 days 96%
Updates
Times in UTCAs posted by Crusoe
This incident has been resolved.
Most affected instances in our Ohio region are back in service. A small number are still unavailable while we finish hardware checks and the last repairs. We’ll keep you posted on further developments
We have restored additional capacity in us-east2-a and are validating each host before returning it to service. Some affected customers are now fully restored, and we continue to return capacity to the remaining impacted customers. The remaining affected hardware will stay offline until facility repairs and safety checks are finished, and we don’t yet have a time for full restoration. We will post an update in 24 hours, or as events warrant.
Work to address the facility issue in us-east2-a continues. The affected hardware will stay offline until facility repairs and safety checks are complete, and it will be brought back online as that work allows. We don’t yet have a time for full restoration. Our teams continue to move impacted instances onto other available capacity in us-east2-a where we can. We will post an update in 24 hours, or as events warrant.
We have restored part of the affected capacity in us-east2-a and continue to move impacted instances onto other available capacity where we can. The remaining affected hardware will stay offline until facility repairs and safety checks are finished, and we don’t yet have a time for full restoration. We will post an update in 24 hours, or as events warrant.
Work to address the facility issue in us-east2-a continues to progress. The hardware that's still affected will stay offline until facility repairs and safety checks are finished, and we don't yet have a time for full restoration. Our teams are still moving impacted instances onto other available capacity in us-east2-a where we can. We will post updates on further developments within the next 24 hours.
Recovery work for the facility issue in us-east2-a is ongoing. The remaining affected hardware will stay powered off until required facility work and safety inspections are complete. We don’t have an estimated restoration time yet, and we’ll share one as soon as those inspections are done. In the meantime, we’re restoring affected instances on other available capacity in us-east2-a where possible, and a number of instances are already back online. If your instances are affected, our customer success team is in contact with you directly. We’ll post another update by 23:00 UTC
We’ve started restoring power to part of the affected hardware in us-east2-a, and some instances will begin to come back online. The rest of the affected hardware will stay powered off while the facility issue is being remediated. Our teams are actively working on recovery, and we’ll post updates as events warrant.
As a safety precaution, we’ve shut off power to the affected hardware in us-east2-a. Instances running on that hardware are now powered off. Power won’t be restored until the area has been confirmed safe. Our teams are working on recovery, and we’ll post another update within 90 minutes.
We’re investigating an issue at one of our data center facilities that is affecting a subset of compute instances in us-east2-a. Some instances are currently unavailable. As a safety precaution, we’re powering down some additional hardware in the affected area. Instances on that hardware will become unavailable during this time. Our teams are actively working on this, and we’ll post another update within 30 minutes.
Affected components
4Crusoe in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
9
Median duration
3 h 54 min
This incident
20× the median
Other Crusoe incidents
All incidentsCrusoe·Storage accessibility issues in eu-norway1
This incident has been resolved.
Crusoe·A subset of VMs are showing as UNSPECIFIED in our us-east2 region
This incident has been resolved.
Crusoe·Networking issue affecting service connectivity
We identified general network errors affecting service connectivity in our us-east1 region. The issue has been resolved and services are operating normally.
Crusoe·VM and CMK cluster creation issue in us-east2 region
This incident has been resolved.
Follow Crusoe
Your coding agent knows when Crusoe is down, and tells you when a failure is theirs, not yours. You can also get Crusoe incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "crusoe" and tell me if Crusoe has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=crusoe/feed subscribe https://outages.cc/feed.xml?providers=crusoeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane