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 105 OVHcloud outages since October 2025. The 105 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major April 16, 2026

April 2026: [EU-WEST-PAR][Storage] - Object Storage Incident Notification

Detected Apr 16, 2026 8:56 AM EDT · Resolved Apr 16, 2026 11:12 AM EDT · Duration about 2 hours

OVHcloud's object storage service in the EU-WEST-PAR region experienced a complete outage for 2.3 hours, causing customers to encounter 503 errors when attempting to access their storage. The incident affected all availability zones (EU-WEST-PAR-A, B, and C) and was caused by an unexpected infrastructure failure. The service was fully restored after teams investigated and resolved the underlying infrastructure issue.

Major April 15, 2026

April 2026: [DE][Databases] - Databases MongoDB incident notification

Detected Apr 15, 2026 4:07 AM EDT · Resolved Apr 15, 2026 6:18 PM EDT · Duration about 14 hours

OVHcloud experienced a major incident affecting their PCI-Databases MongoDB service in the DE1 region from April 15, 2026 04:10 UTC to 22:10 UTC, lasting 14.2 hours. Some MongoDB databases became temporarily unavailable, preventing affected customers from accessing their database services. The incident was identified and linked to a related public cloud issue, with services gradually restored and the incident fully resolved by the end time.

Major April 15, 2026

April 2026: [DE1][Compute - Instance] - Instance incident notification

Detected Apr 15, 2026 3:46 AM EDT · Resolved Apr 15, 2026 5:04 AM EDT · Duration about 1 hour

OVHcloud experienced a major incident affecting their Compute - Instance service in the DE1 region due to an unexpected infrastructure failure. Some instances in the DE1 region became temporarily unreachable, preventing affected customers from accessing and using their instances. The incident was resolved after approximately 4 hours, with service fully restored.

Major April 13, 2026

April 2026: [GRA][Network] - Network incident notification

Detected Apr 13, 2026 5:30 AM EDT · Resolved Apr 13, 2026 8:02 AM EDT · Duration about 3 hours

OVHcloud experienced a network incident in the GRA region from 09:25 to 11:57 UTC on April 13, 2026, affecting network connectivity and public network management across six data centers (GRA1, GRA3, GRA5, GRA7, GRA9, GRA11). The incident was caused by an unexpected underlying infrastructure malfunction, with 80% of services restored partway through and full resolution achieved after 2.5 hours.

Minor April 8, 2026

April 2026: [GRA9][Containers & Orchestration] - Managed Kubernetes Service Incident Notification

Detected Apr 8, 2026 5:33 AM EDT · Resolved Apr 8, 2026 6:23 AM EDT · Duration about 1 hour

OVHcloud's Managed Kubernetes Service clusters in the GRA9 region experienced latency issues for 50 minutes on April 8, 2026, from 09:06 to 10:12 UTC. Customers faced delays when trying to access their Kubernetes clusters due to a related incident affecting the underlying infrastructure. The issue was identified within 27 minutes and fully resolved by OVHcloud's teams.

Major April 8, 2026

April 2026: [GRA9][Network] - API Network incident notification

Detected Apr 8, 2026 5:19 AM EDT · Resolved Apr 8, 2026 6:23 AM EDT · Duration about 1 hour

OVHcloud experienced a software issue that caused the Public Cloud Network API in the GRA9 region to become unavailable for 1.1 hours on April 8, 2026. Customers were unable to create, start, or manage Public Cloud instances and attach new volumes, though existing running instances remained unaffected. The incident was resolved after teams investigated and fixed the underlying software problem.

Major April 2, 2026

April 2026: [EU][Identity, Security & Operations] - Service Logs Incident Notification

Detected Apr 2, 2026 6:42 AM EDT · Resolved Apr 2, 2026 9:46 AM EDT · Duration about 3 hours

OVHcloud's Service Logs feature in the EU region experienced a complete outage from 10:10 to 13:45 UTC on April 2, 2026, lasting 3.1 hours due to an unexpected underlying infrastructure malfunction. Customers were unable to access logs for their managed services or subscribe to logs for new services during this period. The incident was resolved after teams identified the root cause and restored service functionality.

Major April 1, 2026

April 2026: [GRA9][Network] - Load Balancer incident notification

Detected Apr 1, 2026 10:54 AM EDT · Resolved Apr 1, 2026 12:09 PM EDT · Duration about 1 hour

OVHcloud experienced a Load Balancer service disruption in the GRA9 region from 14:03 to 16:00 UTC on April 1st, 2026, caused by an unexpected underlying infrastructure malfunction. The incident prevented customers from performing load balancer management operations and caused temporary unavailability of the Load Balancer service in that region. The issue was resolved after approximately 1.2 hours once teams identified and fixed the infrastructure problem.

Minor April 1, 2026

April 2026: [GRA][Containers & Orchestration] - Managed Private Registry incident notification

Detected Apr 1, 2026 10:15 AM EDT · Resolved Apr 1, 2026 12:09 PM EDT · Duration about 2 hours

OVHcloud's Managed Private Registry service in the GRA region became temporarily unavailable from 13:54 to 14:04 UTC on January 4, 2026, preventing some customers from accessing and using their registries. The 10-minute outage was caused by another related incident affecting the infrastructure. Service was fully restored and remains under monitoring to ensure stability.

Minor March 31, 2026

March 2026: [GRA1/7/11][Storage] - Block Storage incident notification

Detected Mar 31, 2026 10:42 AM EDT · Resolved Mar 31, 2026 2:34 PM EDT · Duration about 4 hours

OVHcloud experienced a Block Storage incident in regions GRA1, GRA7, and GRA11 caused by an unexpected underlying infrastructure malfunction, resulting in low performance and latency issues for customers accessing their storage. The incident lasted 3.9 hours from 14:08 to 18:25 UTC on March 31, 2026, with teams implementing a fix and the service fully recovering by the end time.