OVHcloud: [EU-WEST-OR1][Containers & Orchestration] - Managed Kubernetes Service incident notification
Affected components: Containers & Orchestration || Managed Kubernetes Service - US-WEST-OR
Timeline of updates
- investigating
We are currently experiencing an incident affecting our Managed Kubernetes Service offering, which is causing temporary availability issues in the EU-WEST-OR1 region.
Please find the details of this incident below :
Start time : 17/11/2026 16:13 UTC
Impacted Service(s) : Managed Kubernetes Service control planes are temporarily unreachable.
Customers Impact : Customers are temporarily unable to access and manage their Kubernetes clusters. Deployed workloads are not affected.
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding. - identified
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Managed Kubernetes Service offer on the specific EU-WEST-OR1 region.
Here are some supplementary details :
Start time : 17/11/2026 16:13 UTC
Impacted Service(s) : Managed Kubernetes Service control planes are temporarily unreachable.
Customers Impact : Customers are temporarily unable to access and manage their Kubernetes clusters. Deployed workloads are not affected.
Root Cause : This incident is caused by an intervention that impacted the Managed Kubernetes Service control planes.
Ongoing Actions : 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.
Changes Rewindex caught on this incident
- Major incident: [EU-WEST-OR1][Containers & Orchestration] - Managed Kubernetes Service incident notification
- Incident updated: [EU-WEST-OR1][Containers & Orchestration] - Managed Kubernetes Service incident notification
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on public-cloud.status-ovhcloud.com (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by OVHcloud, started 2026-11-17 17:29 UTC, not resolved, 2 update(s); edited after publishing.
- Title
- [EU-WEST-OR1][Containers & Orchestration] - Managed Kubernetes Service incident notification
- Vendor
- OVHcloud
- Date
- URL
- https://rewindex.com/company/ovhcloud/incidents/tth02dflzrtv
OVHcloud profileRecent OVHcloud incidentsAll outages on November 17, 2026OVHcloud in November 2026MarkdownJSON