Public Cloud Status

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

Start time : 21/10/2026 09:30 UTC End time : 21/10/2026 13:25 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 have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our technical team is still working to resolve the incident, which should be resolved shortly. 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 Storage offer on the specific GRA1 region.

Here are some supplementary details :

Start time : 21/10/2026 09:30 UTC Impacted Service(s) : The Block Storage service in the GRA1 region is temporarily experiencing degraded performance. Customers Impact : Customers may temporarily experience degraded performance on their Block Storage services. 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 apologize for any inconvenience caused and appreciate your understanding.

Resolved: We are pleased to inform you that the incident affecting our AI & Machine Learning offering has been resolved.

Start time : 21/10/2026 07:00 UTC End time : 21/10/2026 08:04 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been fully restored since 21/10/2026 08:04 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 21/10/2026 07:00 UTC Impacted Service(s) : AI Endpoints may have had some performance issues. Customers Impact : Customers may have temporarily experienced slowness when using the AI endpoints.

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are currently investigating an incident affecting our AI & Machine Learning offering, which is causing temporary availability issue on AI Endpoint .

Here are some supplementary details :

Start time : 21/10/2026 07:00 UTC Impacted Service(s) : AI Endpoints may have some performance issue. Customers Impact : Customers may temporarily experience slowness when using the AI endpoints. 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 would like to inform you that the incident affecting our Public Cloud offering has now been resolved.

Please find the details of this incident below :

Start time : 20/10/2026 08:48 UTC End time : 20/10/2026 10:26 UTC Impacted Service(s) : Block Storage volumes hosted on the PCI-RBX-A-volumes_2 cluster in the RBX-A region were unavailable between 08:48 and 09:00 UTC, followed by reduced performance until 10:26 UTC. Customers Impact : Customers were temporarily unable to access their Block Storage volumes between 08:48 and 09:00 UTC, and may have experienced degraded performance on their volumes until 10:26 UTC while the cluster was recovering. Root Cause : This incident was caused by a hardware issue.

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

Identified: We are currently experiencing an incident affecting our Block Storage offering in the RBX-A region.

Please find the details of this incident below :

Start time : 20/10/2026 08:48 UTC Impacted Service(s) : Block Storage volumes hosted on the RBX-A were unavailable between 08:48 and 09:00 UTC and are currently experiencing reduced performance.

Customers Impact : Customers were temporarily unable to access their Block Storage volumes between 08:48 and 09:00 UTC. Since 09:00 UTC, customers may experience degraded performance on their volumes while the cluster is recovering.

Root Cause : This incident is caused by a hardware issue. Ongoing Actions : Our teams are actively working to restore full performance 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 Network API in the GRA11 region has been resolved.

Start time : 16/10/2026 12:30 UTC End time : 16/10/2026 15:30 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 16/10/2026 12:30 UTC Impacted Service(s) : 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. Customers Impact : Customers may have experienced latency and slowness, or encountered errors, when modifying network configurations or creating new resources. Existing resources and running instances remained unaffected. 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 experiencing an incident affecting our Public Cloud offering, which is causing temporary latency issues in the GRA11 region.

Please find the details of this incident below :

Start time : 16/10/2026 12:30 UTC Impacted Service(s) : The Public Cloud Network API in the GRA11 region is currently experiencing slowness, affecting operations on Floating IP, Gateway, Load Balancer, Private network (vRack) and Public network. Existing network configurations continue to operate normally. Customers Impact : Customers may experience latency and slowness, or encounter errors, when modifying network configurations or creating new resources. Existing resources and running instances remain unaffected. 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 Cloud Databases offering has been resolved.

Start time : 16/10/2026 22:16 UTC End time : 17/10/2026 11:30 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 16/10/2026 22:16 UTC Impacted Service(s) : New MySQL services are taking longer than usual to become available. Existing services are not affected. Customers Impact : Customers are temporarily unable to access the new MySQL 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.

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

Start time : 15/10/2026 11:30 UTC End time : 15/10/2026 15:05 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz

We apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 15/10/2026 11:30 UTC Impacted Service(s) : S3 Object Storage is experiencing disconnections and 503 errors in the AP-SOUTH-MUM-1 region. Customers Impact : Customers may experience disconnections and 503 errors when accessing, uploading or retrieving their objects stored in the specified region. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz Ongoing Actions : Our teams are actively working 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: Service has been fully restored since 15/10/2026 11:35 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 15/10/2026 11:30 UTC Impacted Service(s) : Disconnection and 503 errors observed on S3 Object Storage. Customers Impact : Customers were temporarily facing disconnection and 503 errors when trying to access and use their objects located in AP-SOUTH-MUM-1. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/h9zynmg40bbz

We apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 08/10/2026 00:00 UTC End time : 08/10/2026 18:14 UTC Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency was observed for Object Storage S3 in the specified region. Customers Impact : Customers were temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR region. Root Cause : This incident is caused by a software issue.

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 Object Storage S3 offer on the specific EU-WEST-PAR region.

Here are some supplementary details :

Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers may still experience some latency when accessing and using their objects located in EU-WEST-PAR region, though it has significantly decreased. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and a significant reduction in latency has been observed. Our teams remain mobilised to fully 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 Object Storage S3 offering, which is causing temporary latency issue in the EU-WEST-PAR region.

Here are some supplementary details :

Start time : 08/10/2026 00:00 UTC Impacted Service(s) : Latency observed for Object Storage S3 in the specified region. Customers Impact : Customers are temporarily facing latency when trying to access and use their objects located in EU-WEST-PAR region. 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 S3 Object Storage offering in AP-SOUTH-MUM-1 region has been resolved.

Start time : 15/10/2026 06:02 UTC End time : 15/10/2026 06:10 UTC Root Cause : This incident was caused by another incident : https://network.status-ovhcloud.com/incidents/qss8stslpv68

We apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 15/10/2026 06:02 UTC Impacted Service(s) : Disconnection and 503 errors observed on S3 Object Storage. Customers Impact : Customers were temporarily facing disconnection and 503 errors when trying to access and use their objects located in AP-SOUTH-MUM-1. Root Cause : This incident is caused by another incident : https://network.status-ovhcloud.com/incidents/qss8stslpv68

We apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 14/10/2026 08:00 UTC End time : 14/10/2026 15:22 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 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 :

Start time : 14/10/2026 08:00 UTC Impacted Service(s) : The OpenStack Network API in the GRA9 and GRA11 regions is experiencing increased latency. Customers Impact : 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. 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.