Public Cloud Status

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

Start time : 03/07/2026 12:55 UTC End time : 03/07/2026 18:20 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 Compute - Instance offer on the specific GRA1/3/9 regions.

Here are some supplementary details :

Start time : 03/07/2026 12:55 UTC Impacted Service(s) : Some instances in the GRA1/3/9 regions are unreachable. Customers Impact : Some 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 apologize for any inconvenience caused and appreciate your understanding.

Resolved: We had an incident on AI & Machine Learning offer which has now been resolved.

Here are some supplementary details :

Start time : 02/07/2026 15:00 UTC End time : 03/07/2026 08:15 UTC Impacted Service(s) : All models on AI Endpoints have experienced latency and some 503 errors. Customers Impact : Customers experienced increased latency and intermittent 503 errors across all models on AI Endpoints. 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 Compute - Instance offering has been resolved.

Start time : 01/07/2026 17:32 UTC End time : 01/07/2026 18:54 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 Compute - Instance offer on the specific GRA Region.

Here are some supplementary details :

Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Some instances in the GRA7 region are unreachable. Customers Impact : Some 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 apologize for any inconvenience caused and appreciate your understanding.

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

Start time : 01/07/2026 17:32 UTC End time : 01/07/2026 18:54 UTC Root Cause : https://web-cloud.status-ovhcloud.com/incidents/0j01r7j5vsky

We apologize for any inconvenience caused and appreciate your understanding.

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

Here is detail for this incident : Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Some Registries are unreachable in the GRA 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 Containers & Orchestration offering has been resolved.

Start time : 01/07/2026 17:32 UTC End time : 01/07/2026 18:54 UTC Root Cause : https://public-cloud.status-ovhcloud.com/incidents/x3cj8gldm5yx

We apologize for any inconvenience caused and appreciate your understanding.

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

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific DE1 region.

Here are some supplementary details :

Start time : 01/07/2026 17:32 UTC Impacted Service(s) : Customer may have difficulties to do some cluster action Customers Impact : Customer may have difficulties to manage their cluster on DE1 region Root Cause : https://public-cloud.status-ovhcloud.com/incidents/x3cj8gldm5yx 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 offering in BHS1 region has been resolved.

Start time : 29/06/2026 14:07 UTC End time : 29/06/2026 18:40 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: Impacted Service(s) : The block storage service was again unavailable for some customers in BHS1 region between 29/06/2026 17:00 UTC and 29/06/2026 18:00 UTC. Ongoing Actions : Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance.

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 : Customers are now able to access their block storage and normal operations have largely resumed. Ongoing Actions : Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance.

We will keep you updated on the progress and full 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 : The majority of the block storage hosts in BHS1 region are no longer impacted by this incident. Ongoing Actions : Our teams are currently working on the last impacted block storage hosts.

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 Block Storage offer on the specific region BHS1.

Here are some supplementary details :

Start time : 29/06/2026 14:07 UTC Impacted Service(s) : The block storage service is temporarily unavailable for some customers in BHS1 region. Customers Impact : Some customers are unable to access and use their block storage loacted in the specified region. 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.