Provider
OVHcloudIncident detail
[AP-SOUTH-MUM/EU-SOUTH-MIL/EU-WEST-PAR/RBX][Containers & Orchestration] - Managed Kubernetes Service Incident Notification
[AP-SOUTH-MUM/EU-SOUTH-MIL/EU-WEST-PAR/RBX][Containers & Orchestration] - Managed Kubernetes Service Incident Notification
Timeline window
to
Timeline
Incident updates
Updates are normalized from the official source chronology so timeline changes remain easy to scan.
Investigating
We are currently experiencing an event affecting our Managed Kubernetes Service in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions. <b>Start time :</b> 27/05/2026 14:00 UTC Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible. 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 Containers & Orchestration - Managed Kubernetes Service in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions. Here are some supplementary details : <b>Start time :</b> 27/05/2026 14:00 UTC <b>Impacted Service(s) :</b> MKS cluster delivery and deletion is currently unavailable. <b>Customers Impact :</b> Customers are currently unable to create or delete new MKS clusters. <b>Root Cause :</b> A service disruption is currently occurring due to an unexpected infrastructure malfunction. <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.
Resolved
We are pleased to inform you that the incident affecting our Containers & Orchestration - Managed Kubernetes Service offering in AP-SOUTH-MUM / EU-SOUTH-MIL / EU-WEST-PAR / RBX regions has been resolved. <b>Start time :</b> 27/05/2026 14:00 UTC <b>End time :</b> 28/05/2026 13:56 UTC <b>Root Cause :</b> A service disruption is currently occurring due to an unexpected infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.