Public Cloud Outage History

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific region GRA9. Here are some supplementary details : Start time : 08/04/2026 09:06 UTC Impacted Service(s) : Managed Kubernetes Service clusters in GRA9 are temporarily facing latency. Customers Impact : Customers are temporarily facing latency while trying to access their Managed Kubernetes Service clusters. Root Cause : This incident is caused by another incident : https://public-cloud.status-ovhcloud.com/incidents/vwqd4hm52ytq 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our offer on the EU region. Here are some supplementary details : Start time : 02/04/2026 10:10 UTC Impacted Service(s) : Service Logs is unavailable Customers Impact : Customers can no longer access logs for their managed services or subscribe to logs for new ones. 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Storage offer on the specific regions GRA1, GRA7 and GRA11. Here are some supplementary details : Start time : 31/03/2026 14:08 UTC Impacted Service(s) : A low performance is being observed on Block Storage in the specified regions. Customers Impact : Some customers are facing latency when trying to access and use their Block Storage located in GRA1, GRA7 and GRA11. 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.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams implemented a fix and the service is now recovering. Ongoing Actions : During the recovery, customers may experience slightly reduced performance. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in the specific regions. Here are some supplementary details : Start time : 30/03/2026 13:58 UTC Impacted Service(s) : Some instances in BHS1 and BHS3 are temporarily unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in the specific region. Here are some supplementary details : Start time : 30/03/2026 07:22 UTC Impacted Service(s) : Some instances are suddenly unreachable. 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 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.

We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the GLOBAL region. Here are some supplementary details : Start time : 22/03/2026 10:55 UTC Impacted Service(s) : Some instances in the GLOBAL region are unreachable using IAM (Identity and Access Management). Customers Impact : Some customers are temporarily unable to login to their Public Cloud instances using IAM (Identity and Access Management). 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 have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : A fix has been implemented by our teams. Ongoing Actions : Our teams are currently recovering impacted services. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

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 on recovering the impacted services. 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.

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 : 20/03/2026 08:06 UTC Impacted Service(s) : Some instances in GRA5, GRA7, GRA9 and GRA11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access and use their instances in GRA5, GRA7, GRA9 and GRA11 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region. Here are some supplementary details : Start time : 19/03/2026 18:16 UTC Impacted Service(s) : Some instances in the BHS1 region are unreachable. 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 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.

We are currently investigating an incident affecting our MKS offering, which is causing temporary availability issue in GRA11. Here are some supplementary details : Start time : 18/03/2026 13:30 UTC Impacted Service(s) : The creation of new octavia loadbalancers through MKS may have delay. Customers Impact : No issue on existing loadbalancers. Root Cause : https://public-cloud.status-ovhcloud.com/incidents/4s4tt0lqmmk4 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.

We are currently investigating an incident affecting our MongoDB Discovery offering in the GRA Region. Here are some supplementary details : Start time : 10/03/2026 23:40 UTC Impacted Service(s) : New service creation and management operations are temporarily unavailable. Existing database services continue to run but may be impacted due to degraded self-healing capabilities. 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.

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our MongoDB offer on the specific GRA - DE - SBG - UK - BHS and WAW regions. Here are some supplementary details : Start time : 10/03/2026 16:40 UTC Impacted Service(s) : Management operations are temporarily unavailable (e.g., adding users, updating flavors). Existing database services remain operational and continue to serve customer workloads. Customers Impact : 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.

We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : Our teams have replaced the faulty network equipment. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.