Public Cloud Status

Identified: Our provider is still working on resolving the issue affecting our PostgreSQL offering. To avoid issues with geospatial features, we still strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS.

For any questions, please contact your usual point of contact or reach out to our support team.

We will keep you updated on the progress and resolution.

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.

Here are some supplementary details : Start time : 16/03/2026 08:00 UTC Impacted Service(s) : Customers may experience issues when upgrading to PostgreSQL version 18, as the PostGIS extension is currently not functional on this version, potentially preventing the use of geospatial features. As a precaution, we strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

If you have any questions, please contact your usual point of contact or reach out to our support team.

We will keep you updated on the progress and resolution.

Resolved: We are pleased to inform you that the incident affecting our Compute - Instance offer in BHS1, BHS3 and BHS5 regions has been resolved.

Start time : 21/04/2026 11:45 UTC End time : 21/04/2026 13:59 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

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 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

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating an incident affecting our Cloud Compute offering, which is causing temporary functionality issue in BHS1 region.

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 rigion. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

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 has been resolved.

Start time : 21/04/2026 07:51 UTC End time : 21/04/2026 09:40 UTC Root Cause : This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/tpf453cj6rzj

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently experiencing an incident affecting our Containers & Orchestration - Managed Private Registry offering, which is causing temporary functionality issues in the DE region.

Here is detail for this incident : Start time : 21/04/2026 07:51 UTC Impacted Service(s) : Some Registries are unreachable in the De region. Customers Impact : Some customers are temporarily unable to do management operations on their Registries in the specified region. 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.

Resolved: We are pleased to inform you that the incident affecting our Compute - Instance in GRA has been resolved.

Start time : 20/04/2026 12:27 UTC End time : 20/04/2026 12:34 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the Graveline region.

Here are some supplementary details :

Start time : 20/04/2026 12:27 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

Resolved: We had an incident on Object Storage S3 Standard offer in DE region which has now been resolved.

Here are some supplementary details :

Start time : 20/04/2026 09:55 UTC End time : 20/04/2026 11:06 UTC Impacted Service(s) : Object storage service in DE region was temporarily unavailable for some customers. Customers Impact : Some customers were getting 503 error when trying to connect their object storage located in DE region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We thank you for your understanding and patience throughout this incident.

Resolved: We are pleased to inform you that the incident affecting our PCI-Databases offer in AP-SOUTH-MUM region has been resolved.

Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 04:47 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.

Monitoring: Service has been fully restored since 19/04/2026 04:47 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) : Cloud databases services were unavailable in AP-SOUTH-MUM region. Customers Impact : Customers faced difficulties to access their services. Orders and service management were also affected. 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.

Identified: 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.

Investigating: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Customers in the AP-SOUTH-MUM region are temporarily unable to place orders or use management features on their cloud database services. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

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 Storage offer in AP-SOUTH-MUM region has been resolved.

Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 04:44 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.

Monitoring: Service has been fully restored since 19/04/2026 04:44 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) : Issues to access on S3 objects on this region were present. Customers Impact : Customers may have experienced issues downloading or uploading their objects due to 500/503 errors. 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.

Identified: 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.

Investigating: We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the AP-SOUTH-MUM region .

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Issues to access on S3 objects on this region Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

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 offer in AP-SOUTH-MUM region has been resolved.

Start time : 18/04/2026 17:06 UTC End time : 19/04/2026 04:44 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.

Monitoring: Service has been fully restored since 19/04/2026 04:44 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) : Service were degraded for Registry Product on this DC. Customers Impact : Some of customer encountered a degraded service on their registries, images push/pull and some UI were 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.

Identified: 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.

Identified: 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.

Resolved: 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.

Monitoring: 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.

Identified: 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.

Identified: 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.

Resolved: We are pleased to inform you that the incident affecting our Block Storage in AP-SOUTH-MUM-1 region has been resolved.

Start time : 18/04/2026 17:09 UTC End time : 19/04/2026 05:27 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.

Monitoring: Service has been fully restored since 19/04/2026 05:27 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 18/04/2026 17:09 UTC Impacted Service(s) : The block storage service was temporarily unavailable for some customers. Customers Impact : Customers were temporarily unable to access their block storage located in AP-SOUTH-MUM-1 region. 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We are continuing to work on a fix for this issue.

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

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 Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We had an incident on Compute - Instance offer which has now been resolved.

Here are some supplementary details :

Start time : 16/04/2026 16:19 UTC End time : 16/04/2026 16:26 UTC Impacted Service(s) : Some instances in the GRA1 region were unreachable. Customers Impact : Customers were temporarily unable to access and use their instances in the GRA1 region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We thank you for your understanding and patience throughout this incident.

Resolved: We are pleased to inform you that the incident affecting our Storage offering has been resolved.

Start time : 16/04/2026 11:35 UTC End time : 16/04/2026 14:48 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the PAR region.

Here are some supplementary details :

Start time : 16/04/2026 11:35 UTC Impacted Service(s) : The object storage service is temporarily unavailable. Customers Impact : Customers in the EU-WEST-PAR region may temporarily encounter 503 errors on their object storage. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

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 PCI-Databases has been resolved.

Start time : 15/04/2026 04:10 UTC End time : 15/04/2026 22:10 UTC Root Cause : This incident is related by : https://public-cloud.status-ovhcloud.com/incidents/2v5b4kyjttxj

We apologize for any inconvenience caused and appreciate your understanding.

Identified: 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.

Identified: 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.

Investigating: We are currently experiencing an event affecting our PCI-Databases offer.

Start time : 15/04/2026 04:10 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.

Resolved: We are pleased to inform you that the incident affecting our Compute - Instance has been resolved.

Start time : 15/04/2026 04:10 UTC End time : 15/04/2026 08:10 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

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 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.

Investigating: We are currently experiencing an event affecting our Compute - Instance offer.

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.

Resolved: We had an incident on Storage offer which has now been resolved.

Here are some supplementary details :

Start time : 15/04/2026 05:00 UTC End time : 15/04/2026 07:16 UTC Impacted Service(s) : The block storage service was temporarily unavailable for some customers. Customers Impact : Some customers were temporarily unable to access their storage located in ERI1. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We thank you for your understanding and patience throughout this incident.