Crusoe: Crusoe Container Registry (CCR) Maintenance – us-east1-a
Affected components: Container RegistryContainer Registry - Container Registry
Timeline of updates
- scheduledEdited
Date: 27 October 2026
Start Time: 1700 PDT (0000 UTC, 28 October)
End Time: 1740 PDT (0040 UTC, 28 October)
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 largely available, but you may see brief interruptions, typically under one minute, with intermittent 500 (Internal Server Error), 503 (Service Unavailable) or 504 (Gateway Timeout) responses. You may also see 401 responses. This is expected, and standard registry clients will retry automatically with your existing credentials. Image pushes or pulls in progress during an interruption may need to be retried, and pods pulling images at that moment may briefly enter ImagePullBackOff before recovering.
If you are not using CCR, 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, please reach out to support@crusoe.ai.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.crusoecloud.com (opens in new tab).