Public Cloud Status

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The teams have rolled out a fix that has resolved the issue. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

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 MongoDB offering, which is causing temporary availability issue in GRA/DE/UK/RBX/MUM/WAW/SGP/SBG/BHS/EU-WEST-PAR/EU-SOUTH-MIL.

Here are some supplementary details :

Start time : 16/03/2026 14:00 UTC Impacted Service(s) : New service creation is temporarily unavailable. Existing database services continue to run. Customers Impact : Customers are temporarily unable to order new MongoDB services in regions GRA/DE/UK/RBX/MUM/WAW/SGP/SBG/BHS/EU-WEST-PAR/EU-SOUTH-MIL 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 MongoDB Discovery offering has been resolved.

Start time : 10/03/2026 23:40 UTC End time : 13/03/2026 09:00 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: MongoDB Discovery offering has been fully restored since 13/03/2026 09:00 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 10/03/2026 23:40 UTC Impacted Service(s) : New service creation and management operations were temporarily unavailable. Existing database services continued to run but might have been impacted due to degraded self-healing capabilities. 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 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.

Resolved: We had an incident on Storage offer which has now been resolved.

Here are some supplementary details :

Start time : 13/03/2026 07:20 UTC End time : 13/03/2026 08:15 UTC Impacted Service(s) : Severe network traffic disruptions on the S3 object storage clusters between 7:20 and 7:30 UTC. From 7:30 to 8:15 UTC, network instability persisted, causing 500/503 errors and authentication problems. Customers Impact : Customers may have encountered 500/503 errors and authentication issues. Root Cause : This incident was caused by this incident : https://network.status-ovhcloud.com/incidents/dt09splp43wh

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

Resolved: We had an incident on Containers & Orchestration offer that impacted the Load Balancer and Managed Kubernetes Service in GRA11 which has now been resolved.

Here are some supplementary details :

Start time : 12/03/2026 15:00 UTC End time : 12/03/2026 19:30 UTC Impacted Service(s) : Network perturbations were temporarily observed on the Load Balancer and Managed Kubernetes Service in GRA11. Customers Impact : Customers were temporarily facing issues using the Load Balancer and Managed Kubernetes Service in the specified region. Root Cause : This incident was caused by this incident: https://public-cloud.status-ovhcloud.com/incidents/2t9ck6jjtylr

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

Start time : 12/03/2026 15:00 UTC End time : 12/03/2026 19:30 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 functionality issue in the GRA11 region.

Here are some supplementary details :

Start time : 12/03/2026 15:00 UTC Impacted Service(s) : Creation of new Public cloud instances is temporarily unavailable. Also, network instabilities are being observed. Customers Impact : Customers are temporarily unable to create new Public Cloud instances and modify network configurations of their existing instances. 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.

Investigating: We are currently experiencing an event affecting our 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 Managed Kubernetes Service offer has been resolved.

Start time : 12/03/2026 09:11 UTC End time : 12/03/2026 10:21 UTC Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: We had an incident on Managed Kubernetes Service offer which has now been resolved. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 12/03/2026 09:11 UTC End time : 12/03/2026 10:21 UTC Impacted Service(s) : All MKS Clusters on GRA11 are experiencing slow APIServer access from Worker Nodes. Customers Impact : Access to the MKSCluster APIServer is slow from some Worker Nodes, which can impact applications that frequently interact with the APIServer. Ongoing Actions : Our teams are continuing to monitor the system to ensure stable service.

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

Start time : 11/03/2026 17:00 UTC End time : 11/03/2026 19:35 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 functionality issue in the GRA11 region].

Here are some supplementary details :

Start time : 11/03/2026 17:00 UTC Impacted Service(s) : Creation of new Public cloud instances and modification of network configuration is temporarily unavailable. Customers Impact : Customers are temporarily unable to create new Public Cloud instances and modify network configurations of their existing instances. 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 AI & Machine Learning offer has been resolved.

Start time : 04/03/2026 10:00 UTC End time : 11/03/2026 07:00 UTC Root Cause : This incident was caused by a software issue.

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 the latest update on the situation: Update : Latency is still being observed on the LLama3.3-70B model. Our teams are actively monitoring the situation to ensure long-term stability. Ongoing Actions : The root cause of the incident has been identified, and our teams remain fully mobilised to restore normal service as quickly as possible.

We will continue to keep you informed about the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

Monitoring: Service has been fully restored since 06/03/2026 10:00 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/03/2026 15:22 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We have new informations regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The issue has been identified and is related to an unusually high load on the LLama3.3-70B model. Our teams are monitoring the situation and working to mitigate the impact. 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 investigating an incident affecting our AI & Machine Learning offering, which is causing temporary latency issue in the LLama3.3-70B model.

Here are some supplementary details :

Start time : 04/03/2026 10:00 UTC Impacted Service(s) : LLama3.3-70B model is experiencing performance issues. Customers Impact : Latency and unavailability can be observed on the customer side. 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 MongoDB offering has been resolved.

Start time : 10/03/2026 16:40 UTC End time : 10/03/2026 23: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 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.

Investigating: We are currently investigating an incident affecting our MongoDB offering in the DE and GRA Region.

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. 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 on our Storage Volume Snapshot (Ceph) offer has now been resolved.

Here is detail for this incident : Start time : 10/03/2026 07:26 UTC End time : 10/03/2026 17:33 UTC Root Cause : This incident was caused by a network equipment issue.

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

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

Investigating: We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the GRA2.

Here are some supplementary details :

Start time : 10/03/2026 07:26 UTC Impacted Service(s) : Some CEPH volumes are not available in this region. Customers Impact : Customers may experience performance degradation and deterioration in their data redundancy. 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 on our Managed Private Registry offer has now been resolved.

Here is detail for this incident : Start time : 10/03/2026 09:47 UTC End time : 10/03/2026 17:33 UTC Root Cause : This incident was caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/myp81nc676b8

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

Identified: We have determined the origin of the incident affecting our Managed Private Registry offer on the GRA Region.

Here are some supplementary details : Start time : 10/03/2026 09:47 UTC Impacted Service(s) : Some registries are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their registries located on the specified region. Root Cause : This incident is caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/myp81nc676b8 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 would like to inform you that we had an incident on our Managed Private Registry. This incident has now been resolved.

Here are some supplementary details : Start time : 10/03/2026 09:47 UTC End time : 10/03/2026 13:51 UTC Impacted Service(s) : Some registries were unavailable for several minutes between 09:47 and 13:51 UTC. Root Cause : This incident was caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/9ty1dd080xgw

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

Resolved: We are pleased to inform you that the incident affecting our Cold Archive offer has been resolved. However, some time will be required to fully clear the backlog.

Start time : 07/11/2025 10:00 UTC End time : 10/03/2026 12:00 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: Please find below an update on the situation:

Update : Archive recovery is still underway. We would like to clarify the situation regarding restorations. In the meantime, if a customer needs to restore a bucket in "archiving" status, he must submit a support ticket (the criticality level is at the customer's discretion) so that we can perform the restoration.
Ongoing Actions : 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: Please find below an update on the situation: Update : The completion rate has now returned to normal levels; however, a considerable amount of time will still be required to fully clear the backlog. Ongoing Actions : 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: Please find below an update on the situation: Update : We continue to see a backlog of archiving operations that began on  07 Nov 2025 10:00 UTC. The backlog is being processed, but the rate of completion remains below normal levels, resulting in extended latency for new archiving requests. No new tasks are being blocked, but they are progressing more slowly than expected. Ongoing Actions : 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: Please find below an update on the situation: Update : We are continuing our archiving efforts, though completion is taking longer than expected. Ongoing Actions : 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: Please find below an update on the situation: Update : We are still catching up on archiving, but it's slower than expected. Ongoing Actions : 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 : Archiving tasks aren't stuck anymore but slowness is observed. As soon as a customer request archiving, the data will be billed as if it were on tape even though it may take a while for the data to actually reach the tape. 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 : We are currently catching up on archiving, but we do not have an estimated time frame to share with you at this time. 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 Cold archive offer on the specific region.

Here are some supplementary details :

Start time : 07/11/2025 10:00 UTC Impacted Service(s) : Archiving tasks are temporarily stuck in "Archiving" state. Customers Impact : Customers are temporarily unable to archive their data. 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.

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

Start time : 10/03/2026 07:26 UTC End time : 10/03/2026 10:11 UTC Root Cause : This incident was caused by a cooling system issue.

We apologize for any inconvenience caused and appreciate your understanding.

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

Here are some supplementary details :

Start time : 10/03/2026 07:26 UTC Impacted Service(s) : Some CEPH volumes were not available in this region. Customers Impact : Customers may have experienced performance degradation and deterioration in their data redundancy. Root Cause : This incident was caused by a network equipment issue.

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 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.

Investigating: We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the GRA2.

Here are some supplementary details :

Start time : 10/03/2026 07:26 UTC Impacted Service(s) : Some CEPH volumes are not available in this region. Customers Impact : Customers may experience performance degradation and deterioration in their data redundancy. 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.

Investigating: We are currently experiencing an event affecting our Storage offer.

Start time : 10/03/2026 07:26 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.