Public Cloud Status

Investigating: We are currently investigating an incident affecting our Management offering, which is causing temporary latency issue in the US-WEST-LZ-SEA.

Here are some supplementary details :

Start time : 24/10/2025 13:49 UTC Impacted Service(s) : The API in the US-WEST-LZ-SEA region is temporarily degraded. Customers Impact : Customers may have error on the API 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 the UK1 region has been resolved.

Start time : 23/10/2025 18:55 UTC End time : 23/10/2025 19:26 UTC Root Cause : This incident was caused by a software issue.

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 latency issue in the UK1 region.

Here are some supplementary details :

Start time : 23/10/2025 18:55 UTC Impacted Service(s) : The API service is temporarily facing degradation. Customers Impact : Customers are temporarily facing slowness while performing actions via the API. 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 regions BHS1, BHS3 and BHS5 has been resolved.

Start time : 22/10/2025 14:27 UTC End time : 22/10/2025 14:50 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been fully restored since 22/10/2025 14:50 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 22/10/2025 14:27 UTC Impacted Service(s) : Some instances in BHS1, BHS3 and BHS5 regions were unreachable. Customers Impact : Some customers were temporarily unable to access and use their public cloud instances in the specified regions Root Cause : A service disruption occurred due to an unexpected 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 Compute - Instance offer on the specific regions.

Here are some supplementary details :

Start time : 22/10/2025 14:27 UTC Impacted Service(s) : Some instances in BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : Some customers are temporarily unable to access and use their public cloud instances in the specified regions Root Cause : A service disruption occurred due to an unexpected 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.

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

Start time : 22/10/2025 05:55 UTC End time : 22/10/2025 06:25 UTC Root Cause : This incident was du to this change : https://network.status-ovhcloud.com/incidents/tg2nwytzzrk8

We apologize for any inconvenience caused and appreciate your understanding.

Investigating: We are continuing to investigate this issue.

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

Here are some supplementary details :

Start time : 22/10/2025 05:55 UTC Impacted Service(s) : Customers are experiencing 503 errors and slowdowns on their S3 requests. Customers Impact : Some customers may have an error 503. 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 Block Storage offer which has now been resolved.

Here are some supplementary details :

Start time : 21/10/2025 22:00 UTC End time : 22/10/2025 01:07 UTC Impacted Service(s) : The GRA1 Ceph clusters service was experiencing temporarily degraded performance. Customers Impact : Some customers may have temporarily experienced degraded performance of their Ceph cluster volumes in GRA1. Root Cause : A service disruption occured due to an unexpected 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 Compute - Instance offer has been resolved.

Start time : 21/10/2025 22:00 UTC End time : 22/10/2025 01:07 UTC Root Cause : A service disruption occured due to an unexpected infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We have determined the origin of the incident affecting our Compute - Instance offering in the specific GRA1 regions. Here is detail for this incident : Start time : 21/10/2025 22:00 UTC Impacted Service(s) : The public network for some instances is temporarily unavailable or experiencing latency. Customers Impact : Some customers are temporarily unable to access and use their instances in the specified region. The instances continue to operate normally during the incident. Root Cause : A service disruption occurred due to an unexpected 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.

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

Start time : 21/10/2025 22:00 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 AI & Machine Learning has been resolved.

Start time : 08/09/2025 10:00 UTC End time : 16/10/2025 15:00 UTC Root Cause : A service disruption occurred due to an unexpected 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 : Customers using the Llama3.3-70B service are experiencing slowness. Our technical team is working actively on resolving 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.

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 continuing to work on a fix for the issue causing latency on Llama3.3-70B.

We will keep you updated on the progress and resolution.

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 continues to work on a fix causing latency on Llama3.3-70B. 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 have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : A fix is still being worked on by our team. 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 AI & Machine Learning offering, which is causing temporary latency issue in the global region.

Here are some supplementary details :

Start time : 08/09/2025 10:00 UTC Impacted Service(s) : Latency on Llama3.3-70B. Customers Impact : Customers using Llama3.3-70B may experience latency. Root Cause : A service disruption occured due to an unexpected infrastructure malfunction. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible. Workaround : Customers can temporarily use a similar model available on our website.

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

Start time : 20/10/2025 19:34 UTC End time : 20/10/2025 22:51 UTC Root Cause : A service disruption occured due to an unexpected 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 continuing to work on a solution to the issue affecting our Compute - Instance offering.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We have determined the origin of the incident affecting our Compute - Instance offering in the specified region.

Here is detail for this incident : Start time : 20/10/2025 19:34 UTC Impacted Service(s) : Some instances in the BHS5 region are temporarily unavailable. Customers Impact : Some customers are temporarily unable to access and use their instances in the specified region. Root Cause : A service disruption occurred due to an unexpected 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 Data & Analytics offer has been resolved.

Start time : 20/10/2025 00:00 UTC End time : 20/10/2025 10:30 UTC Root Cause : This incident was caused by an outage from our provider's side.

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.

Here are some supplementary details :

Start time : 20/10/2025 00:00 UTC Impacted Service(s) : Jobs, projects, applications, api and superset service are temporarily degraded. Customers Impact : Customers using images on dockerhub may face degradation services with new pods. Root Cause : This incident is caused by an outage from our provider's side. 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 currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue with new pods.

Here are some supplementary details :

Start time : 20/10/2025 00:00 UTC Impacted Service(s) : Jobs, projects, applications, api and superset service are temporarily degraded. Customers Impact : Customers using images on dockerhub may face degradation services with new pods. 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.

Investigating: We are currently experiencing an event affecting our Data Platform 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 are pleased to inform you that the incident affecting our Storage offering has been resolved.

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

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 : Our technical team is continuing to work on a solution to the issue causing degraded performance of our Ceph cluster volumes in GRA11.

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 latency issue in region GRA11.

Here are some supplementary details :

Start time : 17/10/2025 17:00 UTC Impacted Service(s) : The GRA11 Ceph cluster service is experiencing temporarily degraded performance. Customers Impact : Some customers may temporarily experience degraded performance of their Ceph cluster volumes in GRA11.

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 would like to inform you that we had an incident in the BHS1 region. This incident has now been resolved.

Here is detail for this incident : Start time : 18/10/2025 04:53 UTC End time : 18/10/2025 05:30 UTC Impacted Service(s) : Some instances were temporarily unreachable. Customers Impact : Some customers were temporarily unable to access and use their instances located in BHS1. Root Cause : A service disruption occured due to an unexpected infrastructure malfunction.

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