--- service: "Crusoe" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T17:19:34.096Z" url: "https://instatus.com/now/zh-tw/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 官方狀態頁結合起來。