OVHcloud Status · History · Incident #159659
RESOLVED[DE1][Compute - Instance] - Some instances incident notification
Major · Started Nov 11, 2026 · 9:17 AM
OVHcloud Status · History · Incident #159659
RESOLVEDMajor · Started Nov 11, 2026 · 9:17 AM
Duration
1h 8m
Severity
Major
Detection lead
—
User reports
—
Summary
We would like to inform you that the incident affecting our Public Cloud offering in the DE1 region has now been resolved. Please find the details of this incident below : <b>Start time :</b> 11/11/2026 08:35 UTC <b>End time :</b> 11/11/2026 10:23 UTC <b>Impacted Service(s) :</b> Some instances in the DE1 region were temporarily unavailable. <b>Customers Impact :</b> Customers were temporarily unable to access their instances located in the DE1 region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Started
Nov 11, 2026 · 9:17 AM
Resolved
Nov 11, 2026 · 10:25 AM
Duration
1h 8m
Severity
Major
Event timeline
Identified
Nov 11 · 9:17 AM OVHcloudWe are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific DE1 region. Here are some supplementary details : <b>Start time :</b> 11/11/2026 08:35 UTC <b>Impacted Service(s) :</b> Some compute instances are temporarily unavailable. <b>Customers Impact :</b> Some customers are temporarily unable to use their compute instances in the DE1 region. <b>Root Cause :</b> A service disruption occurred due to an unexpected infrastructure failure <b>Ongoing Actions :</b> The incident has been identified and our teams are mobilised to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
Nov 11 · 10:25 AM OVHcloudWe would like to inform you that the incident affecting our Public Cloud offering in the DE1 region has now been resolved. Please find the details of this incident below : <b>Start time :</b> 11/11/2026 08:35 UTC <b>End time :</b> 11/11/2026 10:23 UTC <b>Impacted Service(s) :</b> Some instances in the DE1 region were temporarily unavailable. <b>Customers Impact :</b> Customers were temporarily unable to access their instances located in the DE1 region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Pattern
[US-WEST-OR1][Containers & Orchestration] - Managed Kubernetes Service incident notification
Nov 17, 2026 · 1h 25m
View incident →[GRA][Containers & Orchestration] - Managed Private Registry incident notification
Nov 17, 2026 · < 1m
View incident →[US-CENTRAL-LZ-SLC][LocalZones] - Salt Lake City incident notification
Nov 17, 2026 · 1h 18m
View incident →Add it as a dependency monitor. The Free plan includes one.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.