OVHcloud outage: [EU/CA][Containers & Orchestration] - Managed Kubernetes Service/ Managed Private Registry incident notification

Affected components

• BHS
• BHS5
• DE1
• EU-WEST-PAR
• GRA
• GRA11
• GRA5
• GRA7
• GRA9
• RBX

1. resolvedOct 7, 2026, 14:02 UTC

   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.

2. monitoringOct 7, 2026, 13:45 UTC

   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.

3. identifiedOct 7, 2026, 13:25 UTC

   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

What APIStatus.watch saw

• Oct 7, 2026, 13:13 UTCoperational → partial outage
• Oct 7, 2026, 14:04 UTCpartial outage → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Telnyx: Delayed delivery of 10DLC SMS messages to AT&T destinationsMajor · Oct 6, 2026, 17:38 UTC
• Zoom: Service Degradation Affecting Customer Using Polycom Devices Going OfflineMinor · Sep 25, 2026, 17:45 UTC
• Twilio: MMS Delivery Delays from a Subset of Twilio Long Codes to GCI United StatesMinor · Sep 26, 2026, 03:16 UTC
• Clerk: Development instances only - Apple rejecting emailsMinor · Sep 28, 2026, 15:23 UTC
• Snyk: Issues API V3 Service - DegradedMinor · Oct 3, 2026, 19:49 UTC
• Grafana Cloud: IRM Unable to Send SMS to Thailand, Bangladesh, and Austrian NumbersMinor · Oct 5, 2026, 16:17 UTC
• LiveKit: Investigating reports of elevated RoomService API errorsMinor · Oct 6, 2026, 00:10 UTC
• Twilio: SMS Delivery Failures from Twilio to Movistar El SalvadorMinor · Oct 6, 2026, 20:59 UTC

How often does OVHcloud have incidents?

OVHcloud reported 49 incidents in the last 90 days, 39 of them major or critical. A typical incident lasted 2h 30m. See OVHcloud's uptime and incident history