OVHcloud reported this major-impact incident on its official status page on Oct 13, 2026, 15:22 UTC. It was resolved after 37 min.
Right now OVHcloud is operational. Live OVHcloud status →
We would like to inform you that the incident affecting our Managed Kubernetes Service offering has now been resolved. Please find the details of this incident below : <b>Start time :</b> 13/10/2026 13:45 UTC <b>End time :</b> 13/10/2026 15:20 UTC <b>Impacted Service(s) :</b> Access to the Kubernetes API Server was temporarily unstable. <b>Customers Impact :</b> Customers may have experienced intermittent connectivity issues or errors when accessing the Kubernetes API Server of their clusters located in the specified 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.
We would like to inform you that our service has been fully restored as of 13/10/2026 15:20 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : <b>Start time :</b> 13/10/2026 13:45 UTC <b>Impacted Service(s) :</b> Access to the Kubernetes API Server was temporarily unstable. <b>Customers Impact :</b> Customers may have experienced intermittent connectivity issues or errors when accessing the Kubernetes API Server of their clusters located in the specified region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an incident affecting our Managed Kubernetes Service offering in the SBG5 region. The root cause has been identified. Please find the details of this incident below : <b>Start time :</b> 13/10/2026 13:45 UTC <b>Impacted Service(s) :</b> Access to the Kubernetes API Server is temporarily unstable. <b>Customers Impact :</b> Customers may experience intermittent connectivity issues or errors when accessing the Kubernetes API Server of their clusters located in the specified region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. <b>Ongoing Actions :</b> Our teams are actively working 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.
Overlapping incidents aren't necessarily related.
OVHcloud reported 48 incidents in the last 90 days, 33 of them major or critical. A typical incident lasted 3h 5m. See OVHcloud's uptime and incident history