Public Cloud Status

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

Start time : 26/01/2026 10:08 UTC End time : 26/01/2026 18:10 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

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

Here are some supplementary details :

Start time : 26/01/2026 10:08 UTC Impacted Service(s) : Some instances in the GRA11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access their compute instances. Root Cause : A service disruption occurred due to an unexpected infrastructure failure 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 continuing to investigate this issue.

Investigating: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA11 regions.

Here are some supplementary details :

Start time : 26/01/2026 10:08 UTC Impacted Service(s) : Some instances in the GRA11 regions are unreachable. Customers Impact : Some customers are temporarily unable to access their compute instances. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. 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 the incident on our Storage offering has now been resolved.

Here is detail for this incident : Start time : 26/01/2026 12:45 UTC End time : 26/01/2026 13:00 UTC Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

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

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

Here are some supplementary details : Start time : 26/01/2026 12:45 UTC Impacted Service(s) : Some Volume Snapshot (Ceph) database is temporarily unavailable. Customers Impact : Customers are temporarily unable to access their data located in the specified 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 Compute - Instance has been resolved.

Start time : 23/01/2026 16:38 UTC End time : 23/01/2026 17:25 UTC Root Cause : This incident was caused by a network equipment issue.

We apologize for any inconvenience caused and appreciate your understanding.

Identified: We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue on some instances in the BHS1 region.

Here are some supplementary details :

Start time : 23/01/2026 16:38 UTC Impacted Service(s) : Some instances in BHS1 region were temporarily unavailable. Customers Impact : Some customers were temporarily unable to access and use their instances in the specified region. Root Cause : This incident is caused by a network equipment issue. 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 the incident on our Storage offering has now been resolved.

Here is detail for this incident : Start time : 20/01/2026 20:45 UTC End time : 20/01/2026 20:53 UTC Root Cause : This incident was caused by another incident: https://network.status-ovhcloud.com/incidents/h5f1d9s2kl46

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

Monitoring: Service has been fully restored since 20/01/2026 20:53 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 20/01/2026 20:45 UTC Impacted Service(s) : Object Storage S3. Customers Impact : Customers have experienced connection problems while trying to access Object Storage S3 in WAW. Root Cause : This incident is caused by another incident: https://network.status-ovhcloud.com/incidents/h5f1d9s2kl46

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

Here are some supplementary details :

Start time : 20/01/2026 20:45 UTC Impacted Service(s) : Object Storage S3. Customers Impact : Customers may experience connection problems while trying to access Object Storage S3 in WAW. 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 Compute - Instance in RBX has been resolved.

Start time : 20/01/2026 13:56 UTC End time : 20/01/2026 14:51 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 event affecting our Compute - Instance offer on RBX region.

Start time : 20/01/2026 13:56 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.