OVHcloud Outage History

OVHcloud reported a VPS outage affecting multiple hosts in the VIN region. The incident began on 11:20 PM UTC and impacted VIN Virtual Private Services, causing some VPS instances to be unavailable or unresponsive. The outage lasted about 5 hours 20 minutes and was resolved by 4:40 AM UTC as the VIN VPS component returned to a healthy state. A follow-up status update at 11:59 PM UTC noted a leak and that the data center team was actively working toward a resolution. The provider issued 3 status updates during the incident.

OVHcloud experienced a Hillsboro data center outage on 2026-02-20, impacting HIL / Network Services and HIL / Bare Metal Services. In the Hillsboro region, customers faced network connectivity issues and service interruptions as the affected components went down. The outage lasted about 1 hour and 51 minutes, beginning at Feb 20, 2026 7:39 PM UTC and ending at Feb 20, 2026 9:30 PM UTC.

OVHcloud issued two status updates during the incident: the first acknowledged the issue and said teams were working to restore services, and the second confirmed restoration of the affected components around Feb 20, 2026 9:30 PM UTC.

OVHcloud conducted a backbone maintenance window across multiple regions, including SYD, WAS, and WAW. The maintenance affected a broad set of components spanning Private Cloud, Public Cloud, Network, Bare Metal, and Identity services, with these components temporarily listed as maintenance on the status page. No service impact was reported during the window, and the operation was described as part of ongoing infrastructure improvements. The status page published two updates during the incident, detailing the start and completion of maintenance.

The maintenance began at 6:04 PM UTC and concluded at 8:00 PM UTC, lasting about 1 hour and 56 minutes. Because this was scheduled maintenance, OVHcloud users were not expected to experience outages or degraded performance.

The Data & Analytics MongoDB service experienced a brief event during which creating a new database could remain stuck in the Creating state. Existing MongoDB deployments were not affected.

The issue appeared in two regions (US-EAST-VA-1 and US-WEST-OR-1) and lasted about 11 minutes from 2:54 PM UTC to 3:05 PM UTC. OVHcloud published two official updates during the incident to communicate status and resolution.

OVHcloud conducted a scheduled backbone maintenance starting on Feb 12, 2026 8:05 AM UTC across the OVHcloud backbone infrastructure, affecting a broad set of network, Private Cloud, and Public Cloud components in OVHcloud US and related regions. The maintenance was listed with no service impact for users, and the status page showed multiple components entering maintenance during the window as part of the improvement effort.

The maintenance window lasted about 5 hours and 59 minutes and concluded when the status changed to up at Feb 12, 2026 2:04 PM UTC. The provider issued 2 official status updates during the incident, confirming restoration of services across the affected components.

OVHcloud reported that adding servers to vrack was taking longer than usual, resulting in delays for customers with dedicated Bare Metal servers. The two components impacted were HIL / Bare Metal Services and VIN / Bare Metal Services, affecting server provisioning to vrack.

The degraded provisioning period lasted from 3:09 PM UTC to 4:49 PM UTC (about 1 hour 40 minutes). OVHcloud issued 2 status updates during the incident as they worked to restore normal provisioning.

A VPS host hardware failure caused degradation for OVHcloud's HIL / Virtual Private Services. The degradation began at 3:06 PM UTC and was resolved by 9:49 PM UTC, lasting about 6 hours and 43 minutes. During the window, customers using VPS instances may have experienced intermittent connectivity or reduced performance. The incident involved the HIL / Virtual Private Services component.

OVHcloud experienced a backbone incident that degraded two network services, HIL / Network Services and VIN / Network Services. The incident began at Feb 2, 2026 7:34 PM UTC and OVHcloud described it as a Backbone Incident Notification, with the affected components moving to a degraded state (HIL / Network Services: up -> warn; VIN / Network Services: up -> warn).

Over the following days, OVHcloud continued to update the status, noting that services were back to normal in the incident details and ultimately restoring both components to up at 1:09 PM UTC. The issue spanned multiple days before full recovery.

An outage was detected at OVHcloud affecting 4 VPS hosts in the Vint Hill data center. The VIN / Virtual Private Services component showed as down as the data center investigations were underway.

The incident began at Jan 30, 2026 3:30 PM UTC and was resolved by Jan 30, 2026 7:59 PM UTC, lasting roughly 4 hours and 29 minutes. OVHcloud issued two status updates during the incident, describing the investigation and final recovery.

The OVHcloud BYOIP provisioning feature was unavailable during a maintenance window affecting the ability to order new BYOIP prefixes via API and the Manager. The VIN / Network Services component was listed as maintenance while engineers investigated the root cause. Customers could not order new BYOIP prefixes until further notice. The outage began at 5:04 AM UTC and ended at 11:04 AM UTC, lasting roughly 6 hours. OVHcloud issued two status updates during the incident to communicate progress, and the issue was resolved when the service returned to an Up state. A user report from Perth, Australia around 10:29 UTC indicated a major impact during the window.