--- service: "Crusoe" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T19:24:54.394Z" url: "https://instatus.com/now/ko/crusoe.ai" official_status_page: "https://status.crusoecloud.com" website: "https://crusoe.ai/cloud" --- # Crusoe 다운되었나요? 아니요, 정상이에요. 최근 1시간 동안 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 장애 FAQ ### 지금 Crusoe 다운됐나요? 아니요, 정상이에요. 최근 1시간 동안 0건 보고됨. ### Crusoe이(가) 모두에게 안 되나요, 저만 안 되나요? 당신만 겪는 문제일 수 있어요. Crusoe 제보가 평소 수준이니, 페이지를 새로고침하거나 연결을 확인하거나 로그아웃 후 다시 로그인해 보세요. ### Crusoe에서 사람들은 어떤 문제를 제보하나요? 지난 1시간 동안 Crusoe에서 무엇이 안 되는지 말한 사람이 없습니다. 안 되는 게 있다면 위에서 선택해 다른 사람들도 볼 수 있게 해주세요. ### Crusoe의 마지막 장애는 언제였나요? Crusoe 제보는 최근 30일간 급증하지 않았어요. ### Crusoe에 상태 페이지가 있나요? 네. Crusoe은(는) 공식 상태 페이지에 업데이트를 올리며, 현재 상태는 정상입니다. [상태 페이지로 이동](https://status.crusoecloud.com/) ### Crusoe이(가) 안 되면 어떻게 하나요? 이 페이지와 Crusoe의 상태 페이지에서 업데이트를 확인하고, 몇 분 기다린 후 다시 시도하세요. 재설치는 하지 마세요. 장애라면 해결은 서비스 쪽에서 합니다. ### Crusoe 문제는 어떻게 제보하나요? 이 페이지 상단의 “저도 같은 문제가 있습니다”를 누르고 무엇이 안 되는지 선택하세요. 제보는 1분 안에 실시간 차트에 표시되며, 댓글로 어떤 상황인지 다른 사람에게 알려줄 수도 있습니다. ### Instatus Now는 어떻게 알죠? 이 페이지의 사용자 제보와 매분 확인하는 Crusoe 공식 상태 페이지를 함께 살펴봐요.