OVHcloud Outage History

OVHcloud US VIN / Network Services and OVHcloud US Control Panel (Manager) / OVHcloud US Website Services entered a maintenance window beginning at Dec 11, 2025 8:04 AM UTC due to a possible delay in server delivery. A fix was applied during the window and OVHcloud continued monitoring the situation. The services were restored to normal by Dec 11, 2025 12:09 PM UTC, marking the end of the maintenance window and a total duration of about 4 hours and 5 minutes. The status page included multiple updates to communicate the fix and ongoing monitoring.

During a scheduled maintenance window for OVHcloud's GRA Bare Metal Services, IPMI (management interface) access was temporarily unavailable for racks including GRA0327A05A, GRA0327A06A, GRA0327A06B, GRA0327A06C, GRA0327A07A, GRA0327A05B, GRA0327A07B and GRA0327A07C. The maintenance began at 6:04 AM UTC and ended at 9:55 AM UTC, lasting roughly 3 hours and 51 minutes. OVHcloud noted the work may complete sooner than expected. The incident involved 2 official status updates on the OVHcloud status page, and services returned to normal following the maintenance.

OVHcloud carried out a scheduled backbone maintenance affecting multiple network components to improve overall performance. The maintenance impacted 5 components: HIL / Network Services, HIL / Private Cloud Services, HIL / Bare Metal Services, US-WEST-OR-1 / Public Cloud Services, and HIL / Virtual Private Services. The maintenance window ran from 8:34 AM UTC to 9:34 AM UTC, and OVHcloud stated that no service impact was expected. The provider posted two status updates during the maintenance, and the components returned to their normal state by the end of the window.

OVHcloud US conducted scheduled vRack network switch maintenance at the VintHill Data Center to upgrade the software release version and mitigate a defect that previously caused outages. During the upgrade, vRack connectivity for the affected racks was unavailable for about 1 hour. The maintenance window ran from 1:04 AM UTC to 4:04 AM UTC and impacted two components: VIN / Network Services and VIN / Bare Metal Services.

The service's status page documented the change from up to maintenance and back to up, with a total of 2 official updates during the incident. There were no user reports recorded during this maintenance.

The OVHcloud Public Cloud provisioning was disrupted across multiple North American regions. The incident began with a maintenance action at Dec 2, 2025 11:34 PM UTC affecting Public Cloud Services and related networking components, causing errors when creating new Public Cloud users via the control panel or API. The outage impacted US East, US West, and Central regions, hindering new user provisioning for several hours.

OVHcloud issued four status updates during the incident. On Dec 3, 2025 12:09 AM UTC the issue was acknowledged as an error creating new users. The situation persisted with several regions listed as degraded (warn) through Dec 3, 2025 1:34 AM UTC, before gradually recovering and returning to up across affected regions by Dec 3, 2025 1:04 PM UTC.

OVHcloud placed two Private Cloud components, HIL / Private Cloud Services and VIN / Private Cloud Services, into a maintenance window starting at 6:04 PM UTC. The status message indicated that server delivery may be delayed while a fix was applied and the system was monitored for stability. This maintenance period affected private cloud delivery for the two components and aimed to restore normal operations.

OVHcloud reported a backbone network incident affecting US services, with disruptions to APIv6 and OVHcloud US Website Services in the Miami and Los Angeles points of presence. The issue began at Nov 30, 2025 11:04 PM UTC and was resolved by Dec 1, 2025 12:34 AM UTC, lasting about 1 hour and 30 minutes. OVHcloud stated that engineers were actively working to restore service and would push updates as information became available.

OVHcloud experienced a backbone network incident that disrupted connectivity across multiple regions, affecting Public Cloud Services and Bare Metal Services. The disruption impacted more than a dozen network components, including GRA, HIL, LIM, RBX, SBG, SGP, SYD, VIN, WAW, YNM, YYZ, BHS and ERI, with additional PoPs US-EAST-VA-1 and US-WEST-OR-1 involved. Customers may have experienced degraded connectivity, intermittent outages, and slower access to OVHcloud resources during the incident.

Timeline and response: The backbone incident was first reported at Nov 25, 2025 1:34 PM UTC and OVHcloud published five official status updates over the course of the incident. The provider described ongoing disruptions and implemented measures to restore operations, with several components moving back to up by Nov 25, 2025 3:19 PM UTC and further restorations by Nov 26, 2025 4:05 PM UTC. The incident lasted roughly 26 hours in total.

An incident occurred during a brief maintenance window starting at 2:04 PM UTC due to issues reinstalling servers. To address the problem, OVHcloud placed 13 network locations into maintenance while technicians performed server reinstalls (LIM, WAW, YNM, YYZ, BHS, GRA, HIL, RBX, SBG, SGP, SYD, VIN, ERI). The provider subsequently announced that the issue had been resolved and that they were monitoring the environment. A follow-up update confirmed services returning to normal as systems were brought back online, with maintenance complete by 3:04 PM UTC.

OVHcloud experienced a backbone network incident affecting connectivity at the Miami and Los Angeles Point of Presence. The disruption impacted multiple OVHcloud components, including US-EAST-VA-1 Public Cloud Services and VIN Network, Private Cloud, Bare Metal, and Virtual Private Services. The outage began at Nov 24, 2025 8:05 AM UTC and was resolved by Nov 24, 2025 10:04 AM UTC, lasting roughly 2 hours. OVHcloud labeled the event a Backbone Incident and issued two status updates during the incident as it worked to restore operations. Regional impact was limited to the affected PoP, with services returning to normal after the maintenance window.