OVHcloud Public Cloud Störung und Status

We are currently investigating an incident affecting our Cloud Databases offering, which is causing temporary latency issue in the Global Region. Here are some supplementary details : <b>Start time :</b> 16/10/2026 22:16 UTC <b>Impacted Service(s) :</b> New MySQL services are taking longer than usual to become available. Existing services are not affected. <b>Customers Impact :</b> Customers are temporarily unable to access the new MySQL services. <b>Ongoing Actions :</b> Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progres

We would like to inform you that our service has been fully restored as of 16/10/2026 at 15:30 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : <b>Start time :</b> 16/10/2026 12:30 UTC <b>Impacted Service(s) :</b> The Public Cloud Network API in the GRA11 region experienced slowness, affecting operations on Floating IP, Gateway, Load Balancer, Private network (vRack) and Public network. Existing network configurations continued to operate normally. <b>Customers Impact :</b> Customers may have experienced latency and slowness, o

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: <b>Update :</b> PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18. As a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacte

We are currently experiencing an incident affecting our Object Storage offering in the AP-SOUTH-MUM-1 region. The root cause has been identified. Please find the details of this incident below : <b>Start time :</b> 15/10/2026 11:30 UTC <b>Impacted Service(s) :</b> S3 Object Storage is experiencing disconnections and 503 errors in the AP-SOUTH-MUM-1 region. <b>Customers Impact :</b> Customers may experience disconnections and 503 errors when accessing, uploading or retrieving their objects stored in the specified region. <b>Root Cause :</b> This incident is caused by another incident : https:

Service has been fully restored since 15/10/2026 06:10 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 15/10/2026 06:02 UTC <b>Impacted Service(s) :</b> Disconnection and 503 errors observed on S3 Object Storage. <b>Customers Impact :</b> Customers were temporarily facing disconnection and 503 errors when trying to access and use their objects located in AP-SOUTH-MUM-1. <b>Root Cause :</b> This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/qss8stslpv68 We apologize for any inconv

We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary latency issues in the GRA9 and GRA11 regions. Please find the details of this incident below : <b>Start time :</b> 14/10/2026 08:00 UTC <b>Impacted Service(s) :</b> The OpenStack Network API in the GRA9 and GRA11 regions is experiencing increased latency. <b>Customers Impact :</b> Customers may experience slowness when performing network operations through the API or Horizon, such as creating or modifying networks, ports, floating IPs or security groups. <b>Ongoing Actions :</b> Our team

We would like to inform you that our service has been fully restored as of 13/10/2026 at 15:20 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : <b>Start time :</b> 13/10/2026 15:00 UTC <b>Impacted Service(s) :</b> Access to the Kubernetes API Server was temporarily unstable. <b>Customers Impact :</b> Customers may have experienced intermittent connectivity issues or errors when accessing the Kubernetes API Server of their clusters located in the specified region. <b>Root Cause :</b> A service disruption occurred due to an unexp

Scheduled maintenance is currently in progress. We will provide updates as necessary.

We are continuing to investigate this issue.

Service has been fully restored since 08/10/2026 18:14 UTC. Monitoring remains active to ensure long-term stability. Here are some supplementary details : <b>Start time :</b> 08/10/2026 00:00 UTC <b>Impacted Service(s) :</b> Latency was observed for Object Storage S3 in the specified region. <b>Customers Impact :</b> Customers were temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR region. <b>Root Cause :</b> This incident is caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.