Public Cloud Outage History

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region. Here are some supplementary details : Start time : 02/05/2026 12:18 UTC Impacted Service(s) : Some instances in the LIM1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 are continuing to work on a fix for this issue.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Most instances are now operational again. Ongoing Actions : Our team is working to fix the last remaining instances. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The remaining instances are still being worked on by our teams. 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region. Here are some supplementary details : Start time : 01/05/2026 07:19 UTC Impacted Service(s) : Some instances in the ERI1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 are currently experiencing an ongoing security event affecting our Managed Kubernetes Service. The source of the issue has been identified. Start time : 22/04/2026 08:15 UTC Impacted service(s) : Managed Kubernetes Service (MKS) worker nodes. Customer impact : A recently disclosed security vulnerability may allow a user within a container to gain elevated access on the underlying node. This issue is limited to individual clusters and does not impact other customers or the managed control plane. Customers running shared or multi-tenant workloads within the same cluster should consider this issue with higher priority. Other OVHcloud managed services (MPR, MRS) are patched transparently by OVHcloud, no customer action required. Root Cause : This incident is caused by a software issue. Workaround : A temporary mitigation is available to reduce the risk while we prepare a permanent fix. Instructions are available in our dedicated blog post: https://blog.ovhcloud.com/copy-fail-cve-2026-31431-how-to-rapidly-protect-ovhcloud-mks-clusters-from-the-linux-kernel-zero-day Please note that applying this mitigation is optional and remains under your responsibility. If the vulnerability has already been exploited on your cluster, this mitigation will not remediate any pre-existing compromise Ongoing actions : Our teams are actively working on a permanent fix. Updated versions are expected to be available later today. We will share further details and update instructions as soon as they are ready. We will keep you informed of any progress. Thank you for your understanding.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offering, which is causing temporary functionality issue in the FR region. Here are some supplementary details : Start time : 30/04/2026 08:18 UTC Impacted Service(s) : Builds of APP or API are temporarily unavailable. Customers Impact : Customers are temporarily unable to build API/APP. Root Cause : This incident is caused by a software issue. 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Object Storage S3 offer on the specific region. Here are some supplementary details : Start time : 28/04/2026 10:25 UTC Impacted Service(s) : You may experience issues accessing your Object Storage S3 service. Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. Root Cause : This incident is caused by a software issue. 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region. Here are some supplementary details : Start time : 24/04/2026 14:40 UTC Impacted Service(s) : Some instances in the RBX10 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 have determined the origin of the issue affecting our Storage offer in BHS region. Here are some supplementary details : Start time : 22/04/2026 13:22 UTC Impacted Service(s) : Customers may experience difficulties accessing their services. Customers Impact : Customers may experience 503 errors in BHS region. 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Cloud Compute offer on the specific regions BHS1, BHS3 and BHS5. Here are some supplementary details : Start time : 21/04/2026 11:45 UTC Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. 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 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.

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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific AP-SOUTH-MUM. Here are some supplementary details : Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Service degraded for Registry Product on this DC. Customers Impact : Some of customer may encounter a degraded service on their registries, images push/pull are not available and some UI may be unavailable. 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.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : 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.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : 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.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offer on the specific DE/GRA regions. Here are some supplementary details : Start time : 15/04/2026 07:10 UTC Impacted Service(s) : Some MongoDB databases are temporarily unavailable. Customers Impact : Some customers are temporarily unable to use their MongoDB databases. Root Cause : This incident is related by : https://public-cloud.status-ovhcloud.com/incidents/2v5b4kyjttxj 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.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Some services are available again 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific DE1 region. Here are some supplementary details : Start time : 15/04/2026 07:10 UTC Impacted Service(s) : Some instances in the DE1 region region are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in the DE1 region. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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.