--- service: "Crusoe" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T11:00:42.810Z" url: "https://instatus.com/now/ms/crusoe.ai" official_status_page: "https://status.crusoecloud.com" website: "https://crusoe.ai/cloud" --- # Adakah Crusoe terganggu? Tidak, ia berfungsi. 0 laporan sejam lepas. ## Kemas kini rasmi - **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. ## Soalan lazim gangguan Crusoe ### Adakah Crusoe terganggu sekarang? Tidak, ia berfungsi. 0 laporan sejam lepas. ### Adakah Crusoe terganggu untuk semua orang atau saya sahaja? Nampaknya hanya anda yang mengalaminya. Laporan untuk Crusoe berada pada tahap biasa, jadi cuba muat semula halaman, semak sambungan, atau log keluar dan log masuk semula. ### Apakah masalah yang dilaporkan orang tentang Crusoe? Tiada siapa yang menyatakan apa yang rosak pada Crusoe dalam sejam yang lalu. Jika sesuatu tidak berfungsi untuk anda, pilihnya di atas supaya orang lain dapat melihat. ### Bila gangguan Crusoe yang terakhir? Laporan untuk Crusoe tidak melonjak dalam 30 hari lepas. ### Adakah Crusoe mempunyai halaman status? Ada. Crusoe menyiarkan kemas kini di halaman status rasminya, yang kini menunjukkan: beroperasi. [Pergi ke halaman status](https://status.crusoecloud.com/) ### Apa yang boleh saya buat jika Crusoe tidak berfungsi? Semak halaman ini dan halaman status Crusoe untuk kemas kini, dan tunggu beberapa minit sebelum mencuba lagi. Tak perlu pasang semula: jika ia gangguan, pembaikan di pihak mereka. ### Bagaimana saya melaporkan masalah Crusoe? Tekan “Saya juga ada masalah” di bahagian atas halaman ini dan pilih apa yang tidak berfungsi. Laporan anda muncul pada carta langsung dalam masa seminit, dan anda boleh meninggalkan komen untuk memberitahu orang lain apa yang anda lihat. ### Bagaimana Instatus Now tahu? Kami gabungkan laporan daripada orang di halaman ini dengan halaman status rasmi Crusoe, yang kami semak setiap minit.