OVHcloud Outage History

OVHcloud experienced a brief outage affecting Nutanix cluster access via the OVHcloud Control Panel for US customers. The incident began at Apr 7, 2025 1:24 PM UTC during a maintenance window and lasted about 12 minutes, with Nutanix cluster access temporarily unavailable. A fix was identified and applied, and OVHcloud monitored the situation.

OVHcloud conducted a scheduled maintenance window that temporarily blocked US customers from accessing the Nutanix cluster via the Control Plane. Nutanix management remained available through Prism Central during the disruption. The maintenance began at 3:05 AM UTC and concluded at 8:07 AM UTC, lasting about 5 hours. The affected components were OVH US Services / Servers: Dedicated Servers and Servers / Servers: Dedicated Servers.

The Nutanix cluster could not be accessed via the OVHcloud Control Plane for US customers, limiting management through the Control Plane while clusters remained manageable via Prism Central. The incident began at Apr 3, 2025 8:25 PM UTC and was resolved by Apr 4, 2025 1:14 AM UTC, lasting about 4 hours and 49 minutes. OVHcloud categorized the incident as a warning and issued updates as the situation evolved, closing the issue when access was restored. The problem affected the Dedicated Servers component and appeared isolated to US-based users.

There were two official updates during the incident as OVHcloud worked to investigate and restore access. There were no notable user reports observed during this time, indicating the impact was focused on a specific region and service area rather than a global outage.

An error during vRack Installation Orders caused a payment issue (error: 409 payment already exists). OVHcloud placed a broad set of services into maintenance to address the problem, affecting OVH US Services and Public Cloud Services including OVHcloud Control Panel, Dedicated Servers, Object Storage, Block Storage, Cloud Instances, and Managed Kubernetes Service among others. The incident lasted about four hours, from Apr 3, 2025 5:04 AM UTC to Apr 3, 2025 9:04 AM UTC. Users likely experienced interruptions configuring resources or accessing affected components during this window.

Status page communications indicated a transition to maintenance at the start of the window and a restoration to normal by the end, with two official updates issued as services were brought back online.

The OVHcloud US Services entered an extended maintenance window beginning at Apr 2, 2025 3:01 AM UTC due to a vRack Installation Order Error that caused payment issues during vRack provisioning. The outage affected 18 components across OVHcloud US offerings, including Dedicated Servers, Key Management Service, Object/Block/Archive Storage, OVHcloud Control Panel, Virtual Private Servers, Cloud Instances, and Managed Kubernetes, among others. Users attempting to order a vRack encountered a payment error described as [409] 'payment already exists'; however, vRacks did not incur charges and orders completed despite the error as OVHcloud technicians worked to resolve the issue. OVHcloud published five official status updates during the incident. The outage began at Apr 2, 2025 3:01 AM UTC and was resolved by Apr 2, 2025 3:04 PM UTC, lasting roughly 12 hours.

The OVHcloud status page reported a PCI host down in US-EAST-VA-2, affecting OVH US Services / Public Cloud Services: Virtual Private Servers in the US-East region. About 45 customer instances were impacted. The outage began at Mar 29, 2025 10:05 PM UTC and was resolved by Mar 29, 2025 10:30 PM UTC, lasting approximately 25 minutes. The root cause was identified and a fix is in progress. The provider issued two status updates during the incident.

An OVHcloud network fault at the Vint Hill Data Center (rack V119E10) disrupted the vRack service and temporarily affected OVH US Dedicated Servers. The outage began on Mar 29, 2025 4:04 AM UTC and lasted roughly 3 hours, with restoration completed by Mar 29, 2025 7:04 AM UTC. Impact was observed on US-based vRack connectivity, with Dedicated Servers components showing downtime during the event. The incident underscores how a localized data center issue can ripple into connected services across the US region.

OVHcloud reported a LocalZone outage in US-East-ATL that broke communication from the US-EAST-LZ-ATL zone to other zones, leaving Cloud Instances in that local zone unavailable or degraded. The incident began on Mar 27, 2025 7:59 PM UTC and was resolved by Mar 28, 2025 12:19 PM UTC, lasting approximately 16 hours and 20 minutes. OVHcloud issued two status updates during the event, first noting the Local Zone impact and later confirming restoration of normal operations. The impact was regional, confined to the US-East-ATL Local Zone, with no indicated global impact.

During a maintenance window, OVHcloud experienced a vRack installation order issue that caused a payment error for customers attempting to create a new vRack. OVHcloud notes that vRacks do not incur charges for customers and that orders can complete despite the error. This affected two dedicated server components in the US region, impacting provisioning workflows for that feature. The maintenance began at Mar 27, 2025 12:04 AM UTC and concluded at Mar 27, 2025 3:05 AM UTC, lasting roughly three hours.

During a maintenance window for OVHcloud's Hosted Private Cloud / Dedicated Cloud, a vRack installation order error occurred. Customers attempting to create a new vRack may have seen a payment already exists error, but the order ultimately completed without charging the customer. This issue pertained to the vRack provisioning flow and did not impact other OVHcloud services.

The outage began at 1:10 AM UTC and was resolved by 8:54 AM UTC, lasting approximately 7 hours and 44 minutes. OVHcloud issued two status updates during the incident, describing the problem as a vRack Installation Order Error and confirming that the team was working to resolve it. The status subsequently returned to normal once the maintenance work concluded.