Provider
OVHcloudIncident detail
[EU/CA][Containers & Orchestration] - Managed Kubernetes Service/ Managed Private Registry incident notification
Resolved incidentMajor1 affected service
Timeline window
to
Get alerted the next time OVHcloud breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Identified
We 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
Service 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
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.
Keep exploring
More from OVHcloud
Neighboring incidents on OVHcloud's timeline and the rest of their record on OutageDeck.