Public Cloud Status

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

Start time : 31/01/2026 06:50 UTC End time : 31/01/2026 06:58 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 GRA3 region.

Here are some supplementary details :

Start time : 31/01/2026 06:50 UTC Impacted Service(s) : Some instances in the GRA3 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 Object Storage offering has now been resolved.

Here is detail for this incident : Start time : 29/01/2026 04:30 UTC End time : 29/01/2026 05:37 UTC Root Cause : This incident was caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/35fw13hg9xfk

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

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

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC Impacted Service(s) : Object Storage was temporarily unavailable. Customers Impact : Customers were temporarily getting 503 errors. Root Cause : This incident is caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/35fw13hg9xfk

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 Object Storage offer on the specific region SGP1.

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC Impacted Service(s) : Object Storage is temporarily unavailable. Customers Impact : Customers are temporarily getting 503 errors. Root Cause : This incident is caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/35fw13hg9xfk 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 Object Storage offer.

Start time : 29/01/2026 04:30 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 would like to inform you that the incident on our Identity, Security & Operations offering has now been resolved.

Here is detail for this incident : Start time : 29/01/2026 04:30 UTC End time : 29/01/2026 05:37 UTC Root Cause : This incident was caused by a software issue.

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

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

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC Impacted Service(s) : The Identity, Security & Operations service was temporarily unavailable. Customers Impact : Customers were temporarily unable to use the Identity, Security & Operations service in the SGP1, SGP2, and MUM regions. 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 Identity, Security & Operations offering, which is causing temporary availability issue in the SGP1/SGP2/MUM regions.

Here are some supplementary details :

Start time : 29/01/2026 04:30 UTC Impacted Service(s) : The Identity, Security & Operations service is temporarily unavailable. Customers Impact : Customers are temporarily unable to use the Identity, Security & Operations service in the SGP1, SGP2, and MUM regions. 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 Identity, Security & Operations offer.

Start time : 29/01/2026 04:30 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 would like to inform you that the incident on our Data Platform offer has now been resolved.

Here is detail for this incident : Start time : 28/01/2026 12:16 UTC End time : 28/01/2026 16:40 UTC Root Cause : This incident was caused by this maintenance : https://public-cloud.status-ovhcloud.com//incidents/20z9wycm45ls

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

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

Here are some supplementary details :

Start time : 28/01/2026 12:16 UTC Impacted Service(s) : Data Platform projects were temporarily unavailable. Customers Impact : Customers were temporarily unable to create and use Data Platform projects

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

Here are some supplementary details :

Start time : 28/01/2026 12:16 UTC Impacted Service(s) : Data Platform projects are temporarily unavailable. Customers Impact : Customers are temporarily unable to create and use Data Platform projects Root Cause : This incident is caused by this maintenance : https://public-cloud.status-ovhcloud.com//incidents/20z9wycm45ls 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 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 Data & Analytics has been resolved.

Start time : 28/01/2026 09:00 UTC End time : 28/01/2026 09:28 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 experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offering.

Here are some supplementary details :

Start time : 28/01/2026 09:00 UTC Impacted Service(s) : The data platform is in degraded mode. Customer projects are temporarily unavailable. 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: 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.