Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

OVHcloud Outage History

Every past OVHcloud outage tracked by IsDown, with detection times, duration, and resolution details.

There were 133 OVHcloud outages since October 2025. The 133 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 28, 2026

May 2026: [GRA5/7/9/11][Compute - Instance] - Some Instances Incident Notification

Detected May 28, 2026 6:14 AM EDT · Resolved May 29, 2026 9:25 AM EDT · Duration 1 day

OVHcloud experienced a major infrastructure malfunction that made compute instances unreachable across four regions (GRA5, GRA7, GRA9, and GRA11) starting May 28, 2026 at 08:00 UTC. The incident also caused private network configuration issues on some instances starting at 15:00 UTC the same day, preventing customers from accessing their cloud instances in these regions. The service was fully restored after 27.2 hours on May 29, 2026 at 13:19 UTC following hardware component replacements and system repairs.

Major May 27, 2026

May 2026: [AP-SOUTH-MUM/EU-SOUTH-MIL/EU-WEST-PAR/RBX][Containers & Orchestration] - Managed Kubernetes Service Incident Notification

Detected May 27, 2026 11:27 AM EDT · Resolved May 28, 2026 10:28 AM EDT · Duration about 23 hours

OVHcloud's Managed Kubernetes Service experienced a major outage across four regions (AP-SOUTH-MUM, EU-SOUTH-MIL, EU-WEST-PAR, and RBX) for 23 hours from May 27-28, 2026. The incident was caused by an unexpected infrastructure malfunction that prevented customers from creating or deleting MKS clusters. The service was fully restored after teams identified the root cause and implemented repairs.

Minor May 25, 2026

May 2026: [GRA1][Storage] - Some CEPH volumes incident notification

Detected May 25, 2026 5:30 AM EDT · Resolved May 25, 2026 2:08 PM EDT · Duration about 9 hours

OVHcloud experienced a storage incident in the GRA1 region from 07:30 to 12:50 UTC on May 25, 2026, lasting approximately 5.3 hours. Some CEPH volumes suffered degraded performance and increased latency due to a network equipment issue. The service was fully restored and remained under monitoring to ensure stability.

Major May 21, 2026

May 2026: [BHS5][Compute - Instance] - Instances incident notification

Detected May 21, 2026 7:07 PM EDT · Resolved May 21, 2026 7:24 PM EDT · Duration 17 minutes

OVHcloud experienced a major incident in the BHS5 region where some compute instances became unreachable due to an unexpected underlying infrastructure malfunction. Customers were temporarily unable to access and use their affected instances in the region. The incident lasted 29 minutes from 22:45 to 23:14 UTC on May 21, 2026, and was fully resolved by OVHcloud's engineering teams.

Minor May 20, 2026

May 2026: [GLOBAL][AI & Machine Learning] - AI Endpoint incident notification

Detected May 20, 2026 5:34 AM EDT · Resolved May 20, 2026 11:40 AM EDT · Duration about 6 hours

OVHcloud experienced a software issue that caused performance problems and temporary availability issues with the gpt-oss-120b model on their AI Endpoints service, preventing customers from using this AI model effectively. The incident lasted approximately 27 hours, starting on May 19, 2026 at 09:00 UTC and was resolved on May 20, 2026 at 12:20 UTC.

Major May 20, 2026

May 2026: [SBG5][Compute - Instance] - Public Cloud Incident Notification

Detected May 20, 2026 5:21 AM EDT · Resolved May 20, 2026 6:39 AM EDT · Duration about 1 hour

OVHcloud experienced a major incident affecting Compute instances in the SBG5 region from 08:54 to 10:16 UTC on May 20, 2026, caused by an unexpected infrastructure failure. Some instances became unreachable, preventing customers from accessing their services in that region. The incident was resolved after 1.3 hours with instances gradually restored to normal operation.

Major May 19, 2026

May 2026: [GRA5][Storage] - Block Storage incident notification

Detected May 19, 2026 1:01 AM EDT · Resolved May 19, 2026 2:13 AM EDT · Duration about 1 hour

An unexpected infrastructure malfunction caused OVHcloud's block storage service to become temporarily unavailable for some customers in the GRA5 region starting at 04:46 UTC on May 19, 2026. Affected customers were unable to access or use their block storage resources during the outage. The incident was resolved after approximately 1.2 hours at 05:55 UTC through infrastructure repairs.

Major May 18, 2026

May 2026: [EU-SOUTH-MILA/B/C][Compute - Instance] - Instance creation incident notification

Detected May 18, 2026 5:17 AM EDT · Resolved May 18, 2026 6:03 AM EDT · Duration about 1 hour

OVHcloud experienced a major incident affecting compute instance creation in their EU-SOUTH-MIL regions (A, B, and C) due to an unexpected underlying infrastructure malfunction. The incident prevented customers from creating new Public Cloud instances, vRack, and LoadBalancer services, with regions A and B restored after 3 days and region C taking the full duration to resolve. The incident lasted from May 15, 2026 12:10 UTC to May 18, 2026 09:54 UTC and has been fully resolved.

Major May 13, 2026

May 2026: [GRA][Compute - Instance] - Incident Notification

Detected May 13, 2026 5:44 AM EDT · Resolved May 13, 2026 7:44 AM EDT · Duration about 2 hours

OVHcloud experienced a major incident affecting their Compute - Instance service in GRA regions (GRA5, GRA7, GRA9, GRA11) from 09:03 to 09:35 UTC on May 13, 2026. The incident was caused by a network equipment issue and was resolved after approximately 32 minutes.

Major May 11, 2026

May 2026: [US-EAST-VA-1][Public Cloud] - Managed Kubernetes Service Incident Notification

Detected May 11, 2026 11:52 AM EDT · Resolved May 11, 2026 2:55 PM EDT · Duration about 3 hours

OVHcloud's Managed Kubernetes Service in the US-EAST-VA-1 region experienced a major incident lasting 3.1 hours, making some instances unreachable and preventing customers from managing or creating new Kubernetes clusters. The service disruption was caused by an unexpected underlying infrastructure malfunction and was fully resolved.