OVHcloud Outage History

OVHcloud reported a vRack Installation Order Error that required a maintenance window across OVH US Services. The incident began at Mar 25, 2025 9:44 AM UTC and ended at Mar 25, 2025 10:44 AM UTC, lasting about one hour. The issue affected 17 components across Dedicated Cloud, Cloud Instances, Virtual Private Servers, Object Storage, Block Storage, Archive Storage, Managed Kubernetes Service, and OVHcloud Control Panels. A payment error (409) occurred during vRack orders, but OVH noted that vRacks do not incur charges and orders can complete despite the error. The status changed from up to maintenance, then back to up.

OVHcloud experienced a multi-component disruption tied to vRack installation and order checkout errors. The issue began at Mar 10, 2025 1:00 PM UTC when affected components were placed in maintenance due to a vRack installation order problem. Over the next several days, customers encountered payment or checkout failures (including error code 409: payment already exists) across five components: Hosted Private Cloud / Dedicated Cloud, Public Cloud Services / Managed Kubernetes Service, OVH US Services / Servers: Dedicated Servers, Servers / Servers: Dedicated Servers, and OVH US Services / OVHcloud Control Panel. The incident remained in a maintenance or degraded state for most of its duration, with a degraded state introduced at Mar 14, 2025 7:25 PM UTC and final resolution later on Mar 19, 2025 3:05 AM UTC.

OVHcloud experienced a brief degraded period affecting vRack installation orders in the United States. During the incident, attempting to install a vRack triggered a payment error with the message 'payment already exists.' OVHcloud notes that vRacks do not incur charges and the orders complete despite the error, but the checkout flow was impaired. The incident began at Mar 6, 2025 10:29 AM UTC and was resolved by Mar 6, 2025 4:04 PM UTC, lasting roughly 5 hours and 35 minutes. OVHcloud issued two status updates during the incident, and the affected components were OVH US Services / Servers: Dedicated Servers and Servers / Servers: Dedicated Servers. Geographic impact was the United States region.

An incident occurred when OVHcloud initiated a maintenance window due to a vRack Installation Order Error that could cause a payment-related issue. The maintenance affected a broad set of OVHcloud US Services and Public Cloud Services, including Dedicated Servers, Object Storage, Cloud Instances, Block Storage, Archive Storage, Virtual Private Servers, and related control panels. Users may have experienced service interruptions or degraded access during the maintenance period.

The outage began at 1:04 AM UTC and was resolved by 1:29 AM UTC. OVHcloud issued 2 status updates during the incident to communicate progress and eventual restoration of services.

The incident began on 12:00 AM UTC with a regional visibility issue in APAC where bandwidth consumption could not be viewed for APAC region servers in the Control Panel. The problem later expanded to Object Storage S3 compatibility problems caused by an AWS SDK upgrade that enforced new checksums, leading to InvalidArgument errors on various S3 operations. The disruption affected multiple OVHcloud services, including Object Storage, Dedicated Servers, the OVHcloud Control Panel, and Public Cloud Services, with several components moved to maintenance as the incident progressed. The situation evolved through multiple status updates, and most services returned to normal by 12:04 PM UTC. The outage lasted about 5 days and 12 hours.

OVHcloud conducted a scheduled Veeam maintenance window across OVH US Public Cloud Services and related components. The status page stated that customers should not expect any impact during the maintenance. The maintenance began at Feb 27, 2025 5:26 PM UTC and concluded at Feb 27, 2025 6:29 PM UTC, lasting approximately 1 hour and 3 minutes. After the maintenance, listed components including Cloud Instances, Object Storage, Block Storage, Hosted Private Cloud, Dedicated Servers, and OVHcloud Control Panel returned to the normal up state.

OVHcloud carried out a scheduled Veeam maintenance across its Public Cloud Services, including Virtual Private Servers, Object Storage, Cloud Instances, and Block Storage. The maintenance began at 4:04 AM UTC and concluded at 7:05 AM UTC, lasting about 3 hours and 1 minute. OVHcloud stated that customers should not expect any impact, and all components returned to normal operation after the maintenance window.

OVHcloud carried out a scheduled Veeam maintenance affecting Public Cloud Services components including Virtual Private Servers, Cloud Instances, Object Storage, Block Storage, and the Managed Kubernetes Service. The maintenance began at 1:00 AM UTC and concluded at 3:05 AM UTC, lasting about 2 hours and 5 minutes. OVHcloud indicated that customers should not expect any impact during the window, and services returned to normal after the maintenance.

OVHcloud performed scheduled Veeam maintenance on its Hosted Private Cloud (Dedicated Cloud), upgrading Veeam managed proxies. The maintenance window began at Feb 25, 2025 3:04 PM UTC and concluded at Feb 26, 2025 12:00 PM UTC, lasting about 20 hours and 56 minutes. Customers were not expected to experience any user impact during this window.

Two official status updates were posted by OVHcloud during the incident, documenting the maintenance and its completion. The affected component was Hosted Private Cloud / Dedicated Cloud, and operation returned to normal by Feb 26, 2025 12:00 PM UTC.

OVHcloud conducted planned maintenance for dedicated servers at the US Vint Hill data center (VH). The planned window was from Feb 24, 2025 12:00 PM UTC to Feb 24, 2025 10:00 PM UTC, with actual work lasting from Feb 24, 2025 2:05 PM UTC to Feb 24, 2025 5:42 PM UTC—roughly 3 hours and 37 minutes. OVHcloud stated there was no expected customer impact, and the status transitioned back to up after the maintenance. The provider issued 2 status updates during the incident.