--- service: "Crusoe" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-10-31T19:04:18.930Z" url: "https://instatus.com/now/be/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? Паведамленні пра Crusoe не раслі за апошнія 30 дзён. ### Ці ёсць у Crusoe старонка статусу? Так. Crusoe публікуе абнаўленні на сваёй афіцыйнай старонцы статусу, дзе цяпер напісана: працуе. [Перайсці на старонку стану](https://status.crusoecloud.com/) ### Што рабіць, калі Crusoe не працуе? Сачыце за абнаўленнямі на гэтай старонцы і на старонцы статусу Crusoe, а перад новай спробай пачакайце колькі хвілін. Не пераўсталёўвайце: калі гэта збой, выпраўленне на іх баку. ### Як паведаміць пра праблему з Crusoe? Націсніце «У мяне таксама праблема» уверсе гэтай старонкі і выберыце, што не працуе. Ваша паведамленне з'явіцца на жывым графіку за хвіліну, а каментарый дапаможа расказаць іншым, што вы бачыце. ### Адкуль Instatus Now гэта ведае? Мы аб'ядноўваем паведамленні людзей на гэтай старонцы з афіцыйнай старонкай статусу Crusoe, якую правяраем кожную хвіліну.