[AP-SOUTH-MUM][Public Cloud] - LocalZone / CEPH / Compute Instance / Managed Kubernetes Service incident notification

Update timeline

1. identified Apr 18, 2026, 10:06 PM UTC

   We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

2. identified Apr 18, 2026, 11:00 PM UTC

   We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some customers using a Managed Kubernetes Service may also be impacted. The management service for instances, volumes, and the load balancer is temporarily unavailable. Customers are currently unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region is also temporarily unavailable. We recommend that customers do not perform any actions on their currently running services. Ongoing Actions : The incident has been identified and our teams and 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.

3. monitoring Apr 19, 2026, 06:33 AM UTC

   Service has been fully restored since 19/04/2026 05:49 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers were temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone were unavailable, and some Ceph volumes in the region were also impacted. Also, some customers using a Managed Kubernetes Service were also impacted. The management service for instances, volumes, and the load balancer were temporarily unavailable. Customers Impact : Some customers were temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Also customers using Managed Kubernetes Service were unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region was also unavailable. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.

4. resolved Apr 19, 2026, 12:11 PM UTC

   We are pleased to inform you that the incident affecting our Public Cloud offer in AP-SOUTH-MUM region has been resolved. Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 05:49 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk We apologize for any inconvenience caused and appreciate your understanding.