OVHcloud Outage History

The incident affected OVHcloud's US network backbone, disrupting network services in the Miami and Los Angeles PoPs. Two components, ERI / Network Services and ERI / Bare Metal Services, entered maintenance during the issue and the disruption lasted about 2 hours and 30 minutes. The outage began at Oct 16, 2025 7:04 AM UTC and was resolved by Oct 16, 2025 9:34 AM UTC. The provider used the status page to communicate the incident, issuing updates as work progressed and confirming service restoration at the end of the window.

OVHcloud reported a backbone incident that disrupted network services at the Miami and Los Angeles Points of Presence, impacting ERI / Bare Metal Services. Customers relying on these network paths experienced connectivity issues and degraded performance during the incident as OVHcloud worked to restore normal operations.

The outage began on 8:04 PM UTC with a Backbone Incident affecting OVHcloud's network in the Miami/Los Angeles PoP. The disruption then extended to dedicated servers in room E102, leaving some servers temporarily unavailable and users unable to access those servers in that room. The issue was localized to these facilities and did not represent a global outage, with restoration completed by 10:44 PM UTC (roughly 2 hours and 40 minutes).

OVHcloud experienced a backbone network incident centered on the Miami and Los Angeles PoPs that disrupted network services across several environments. The disruption affected 5 components, including US-WEST-OR-1 / Public Cloud Services, HIL / Private Cloud Services, HIL / Bare Metal Services, HIL / Network Services, and HIL / Virtual Private Services, with users potentially experiencing intermittent connectivity or degraded performance during the maintenance window. The disruption began at 1:34 AM UTC and was resolved by 3:34 AM UTC.

During the incident, OVHcloud posted two official status updates detailing ongoing maintenance actions and progress toward restoration. By 3:34 AM UTC, all affected components had returned to normal operations.

OVHcloud reported a backbone network incident affecting the HIL / Bare Metal Services in the Miami and Los Angeles PoPs. The disruptions prompted a maintenance window starting at Oct 9, 2025 6:04 AM UTC and lasting about 2 hours, with services restored by Oct 9, 2025 8:04 AM UTC. OVHcloud described the issue as a Backbone Incident Notification and noted active remediation and ongoing updates to affected customers. The incident involved the HIL / Bare Metal Services component and led to degraded network connectivity during the window; the provider issued 2 status updates during the incident, before restoring services.

The outage began on Sep 30, 2025 4:54 PM UTC with disruptions to OVHcloud network services in the Miami/Los Angeles PoP, impacting a broad set of OVHcloud offerings across US regions. Users could experience degraded connectivity, slower provisioning, and, later, delays in server delivery for US-based hardware customization. The issue persisted for over eight days as OVHcloud issue after issue documented ongoing backbone and data-center network disruptions across multiple components.

OVHcloud experienced a series of backbone and regional network incidents beginning mid‑July 2025 that disrupted services across the OVHcloud US footprint and beyond. The outages affected Public Cloud, VPS, Bare Metal, and Private Cloud offerings, with reports of degraded connectivity and intermittent outages across data centers including Hillsboro and Vint Hill, and across US East and West Local Zones. The situation evolved in waves over several weeks, with connectivity restored at times only to be followed by new issues, including VPS provisioning delays and LocalZones outages. The initial backbone disruption is noted to have begun on Jul 16, 2025 7:04 AM UTC and the incident activity continued through September 2025.

The OVHcloud backbone network incident began on Jul 13, 2025 2:35 AM UTC and degraded connectivity across OVHcloud services as latency increased on the CHI-BHS route. This triggered multiple status updates as engineers investigated and worked to restore service. On 4:04 AM UTC a cooling fault was identified at V119G12 in the Vint Hill datacenter, affecting a portion of dedicated servers; the issue progressed to maintenance on 7:04 AM UTC with a broad restoration underway. Full recovery was reported by 6:04 PM UTC. During the incident, a wide set of OVHcloud components across network, bare metal, private cloud, and public cloud services were impacted, leading to degraded performance and intermittent connectivity for customers. The status page documented several updates as engineers worked toward resolution, with services gradually returning to normal by the evening of {{date:2025-07-15}}.

OVHcloud reported a backbone incident affecting the US-WEST-LZ-DEN-A network service, which caused connectivity issues for users in the US-West region. Connectivity has been restored and OVHcloud teams continue investigations to determine the root cause. The incident began at 11:04 PM UTC and was resolved by 3:04 AM UTC, lasting approximately 4 hours. The provider issued 2 status updates during the incident, and the affected component was US-WEST-LZ-DEN-A / Network Services.

An OVHcloud US backbone incident disrupted connectivity across OVHcloud US services, affecting a broad set of components across network, cloud, and infrastructure. The outage impacted US-East and US-West data centers and touched Network Services, the OVHcloud US Control Panel, Public Cloud, Private Cloud, Bare Metal, and related support services. The incident began at Jul 10, 2025 4:04 AM UTC with a backbone disruption; connectivity was briefly reported as restored while teams investigated the root cause, and by Jul 10, 2025 10:05 AM UTC status updates indicated services had returned to normal as maintenance transitioned to up. The outage lasted roughly 6 hours and involved dozens of components across the OVHcloud US footprint. OVHcloud issued two official updates during the incident as teams worked to restore services and determine the underlying issue.