Crusoe Container Registry (CCR) Maintenance in us-east1-a
Crusoe Cloud will be performing two planned maintenance activities on the Crusoe Container Registry (CCR) in us-east1-a on 12 November 2026 to improve reliability and performance. Details for each are below. Maintenance 1 Date: 12 November 2026 Start Time: 1000 PST (1800 UTC) End Time: 1030 PST (1830 UTC) Impact: Crusoe Cloud will be performing planned maintenance on the Crusoe Container Registry (CCR) in us-east1-a to improve reliability and performance. During the maintenance window, CCR in the us-east1-a region will remain available, but you may see a brief interruption of approximately 2–3 seconds. Image pulls already in progress will continue uninterrupted. Image pushes and pulls that start during that interruption may briefly stall but will complete on retry. Standard registry clients retry automatically, so no errors are expected and no action is required. You may also notice slightly slower image pulls for a short period after the maintenance while caches are rebuilt. Maintenan
The latest update from Crusoe.
State
Scheduled
Starts
in 11 d
2026-11-12 18:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Crusoe
Crusoe Cloud will be performing two planned maintenance activities on the Crusoe Container Registry (CCR) in us-east1-a on 12 November 2026 to improve reliability and performance. Details for each are below. Maintenance 1 Date: 12 November 2026 Start Time: 1000 PST (1800 UTC) End Time: 1030 PST (1830 UTC) Impact: Crusoe Cloud will be performing planned maintenance on the Crusoe Container Registry (CCR) in us-east1-a to improve reliability and performance. During the maintenance window, CCR in the us-east1-a region will remain available, but you may see a brief interruption of approximately 2–3 seconds. Image pulls already in progress will continue uninterrupted. Image pushes and pulls that start during that interruption may briefly stall but will complete on retry. Standard registry clients retry automatically, so no errors are expected and no action is required. You may also notice slightly slower image pulls for a short period after the maintenance while caches are rebuilt. Maintenan
Affected components
2Crusoe in the last 90 days
Full historyIncidents in 90 days
5
Days with an incident
9
Median duration
3 h 54 min
This incident
Not comparable
Other Crusoe incidents
All incidentsCrusoe·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.
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.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