--- service: "Crusoe" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T14:26:01.384Z" url: "https://instatus.com/now/zh/crusoe.ai" official_status_page: "https://status.crusoecloud.com" website: "https://crusoe.ai/cloud" --- # Crusoe 故障了吗？ 没有，一切正常. 过去一小时 0 份反馈报告。 ## 官方更新 - **Crusoe Container Registry (CCR) Maintenance in us-east1-a** (SCHEDULED, 2026-11-12T18:00:00.000Z): 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. Maintenance 2 Date: 12 November 2026 Start Time: 1030 PST (1830 UTC) End Time: 1200 PST (2000 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 be unavailable for approximately 1 minute. Image pushes or pulls started or in progress during that minute will fail and will need to be retried and pods pulling images at that moment may briefly enter ImagePullBackOff before recovering. You may also see intermittent 500 (Internal Server Error), 503 (Service Unavailable) or 504 (Gateway Timeout) responses during this period. Standard registry clients retry automatically with your existing credentials, and no data or stored images will be affected. No action is required on your end. If you are not using CCR then these 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. - **Crusoe Cloud Network Maintenance in us-east1-a** (SCHEDULED, 2026-11-06T02:30:00.000Z): Date: 9 November 2026 Start Time: 1830 PST (0230 UTC, 10 November) End Time: 2100 PST (0500 UTC, 10 November) Impact: Crusoe Cloud will be performing planned network maintenance in us-east1-a to prepare for future connectivity features. The work will be carried out on one network gateway at a time and traffic will be moved to healthy gateways before each one is updated, so no downtime is expected. If you use Crusoe load balancers in us-east1-a, existing TCP connections through your load balancer may be reset as traffic is moved between gateways. This may happen more than once during the window. Applications and clients that reconnect automatically will recover within seconds. New connections are not affected and running VMs, clusters, storage and data are not affected. We recommend making sure client applications that use long lived connections through your load balancer are able to reconnect. No other action is required on your end. If you are not using Crusoe load balancers in us-east1-a then 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. - **Crusoe VPC Maintenance in us-east2-a** (COMPLETED, 2026-10-30T01:00:00.000Z): The scheduled maintenance has been completed. - **Crusoe Container Registry (CCR) Maintenance – eu-iceland1-a** (COMPLETED, 2026-10-28T00:40:00.000Z): The scheduled maintenance has been completed. - **Crusoe Container Registry (CCR) Maintenance – us-east1-a** (COMPLETED, 2026-10-28T00:00:00.000Z): The scheduled maintenance has been completed. ## Crusoe 故障常见问题 ### Crusoe 现在挂了吗？ 没有，一切正常. 过去一小时 0 份反馈报告。 ### Crusoe 是所有人都坏了，还是只有我？ 看起来只有你遇到。Crusoe 的反馈量正常，可以试试刷新页面、检查网络连接，或退出后重新登录。 ### 大家反馈了 Crusoe 的哪些问题？ 过去一小时内没有人说明 Crusoe 哪里坏了。如果你遇到问题，请在上方选择，让其他人看到。 ### Crusoe 上次故障是什么时候？ 过去 30 天内，Crusoe 的反馈没有出现激增。 ### Crusoe 有状态页面吗？ 有。Crusoe 会在官方状态页面发布更新，目前显示：运行正常。 [前往状态页面](https://status.crusoecloud.com/) ### Crusoe 无法使用时我可以怎么办？ 查看本页和 Crusoe 的状态页面获取更新，等几分钟再试一次。不用重新安装：如果是服务中断，要由他们那边修复。 ### 如何反馈 Crusoe 的问题？ 点击本页顶部的“我也要反馈问题”，再选择哪里坏了。你的反馈会在一分钟内显示在实时图表上，也可以留言告诉其他人你遇到的情况。 ### Instatus Now 是怎么知道的？ 我们把此页面上用户的反馈，与每分钟检查一次的 Crusoe 官方状态页结合起来。