OVHcloud Status · History · Incident #145662
RESOLVED[EU/CA][Containers & Orchestration] - Managed Kubernetes Service/ Managed Private Registry incident notification
Major · Started Oct 7, 2026 · 1:25 PM
OVHcloud Status · History · Incident #145662
RESOLVEDMajor · Started Oct 7, 2026 · 1:25 PM
Duration
37m
Severity
Major
Detection lead
—
User reports
—
Summary
We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. <b>Start time :</b> 07/10/2026 13:00 UTC <b>End time :</b> 07/10/2026 13:41 UTC <b>Root Cause :</b> This incident was caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t We apologize for any inconvenience caused and appreciate your understanding.
Started
Oct 7, 2026 · 1:25 PM
Resolved
Oct 7, 2026 · 2:02 PM
Duration
37m
Severity
Major
Event timeline
Identified
Oct 7 · 1:25 PM OVHcloudWe are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific regions. Here are some supplementary details : <b>Start time :</b> 07/10/2026 13:00 UTC <b>Impacted Service(s) :</b> Managed Kubernetes Service and Managed Private Registry. <b>Customers Impact :</b> Customers are temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. Existing clusters and their workloads are not impacted. Also, customers are temporarily unable to push and pull their Managed Private registry images located in GRA7, GRA9, BHS5 and EU-WEST-PAR regions. <b>Root Cause :</b> This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t <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.
Monitoring
Oct 7 · 1:45 PM OVHcloudService has been fully restored since 07/10/2026 13:41 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 07/10/2026 13:00 UTC <b>Impacted Service(s) :</b> No more issue observed for Managed Kubernetes Service and Managed Private Registry. <b>Customers Impact :</b> Customers were temporarily unable to create or update Managed Kubernetes Service Clusters, and/or add nodes on their Managed Kubernetes Service Clusters. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
Oct 7 · 2:02 PM OVHcloudWe are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved. <b>Start time :</b> 07/10/2026 13:00 UTC <b>End time :</b> 07/10/2026 13:41 UTC <b>Root Cause :</b> This incident was caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/kdqq2smzfd4t We apologize for any inconvenience caused and appreciate your understanding.
Pattern
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.