[Emergency] Crusoe Container Registry (CCR) Maintenance in us-east1-a
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Crusoe.
State
In progress
Started
Ongoing for
1 h 46 min
Worst impact
Maintenance
Timeline
3 updatesScheduled
1 min 0%
In progress
1 h 45 min 100%
Updates
Times in UTCAs posted by Crusoe
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Maintenance will begin as scheduled in 60 minutes.
Date: 10 November 2026 Start Time: 1700 PST (0100 UTC, 11 November) End Time: 1900 PST (0300 UTC, 11 November) Impact: Crusoe Cloud will be performing planned maintenance on the Crusoe Container Registry (CCR) in us-east1-a to improve reliability and keep the service on a consistent, stable platform version. During the maintenance window the infrastructure supporting CCR in the us-east1-a region will be upgraded in two stages on a rolling basis, one component at a time. Customers may experience up to two brief periods of disruption, each lasting approximately 2 minutes, to registry.us-east1-a.ccr.crusoecloudcompute.com during the window. Image pulls or pushes started during those periods may stall or fail and should complete on retry. No data or stored images will be affected. If you are not using CCR in us-east1-a, this maintenance will have no impact on your workloads. If you have questions regarding your specific workloads or notice persistent issues following the maintenance window
Affected components
2Crusoe in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
12
Median duration
3 h 54 min
This incident
Not comparable
Other Crusoe incidents
All incidentsCrusoe·Compute issue in eu-norway1
Compute and GPU Virtual Machines in eu-norway1 had a partial outage. Crusoe identified the issue and worked to restore service. Crusoe reports that the issue is resolved, and it lasted about 33 hours and 35 minutes.
Crusoe·Storage issue in eu-norway1
Crusoe reports degraded Shared Disks in eu-norway1. The issue is resolved. It lasted 1 hour and 12 minutes.
Crusoe·Facility issue in us-east2-a
This incident has been resolved.
Crusoe·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.
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.live/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.live/feed.xml?providers=crusoe/feed subscribe https://outages.live/feed.xml?providers=crusoeFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane