OVHcloud's Cold Archive service in the RBX region experienced a major incident from November 7, 2025 to March 10, 2026 (approximately 4 months) due to an unexpected infrastructure malfunction. The incident initially caused archiving tasks to become stuck in "Archiving" state, preventing customers from archiving their data, and later resulted in significant processing delays and backlogs even after tasks resumed. The service was eventually restored, though customers requiring restoration of buckets stuck in "archiving" status during the incident needed to submit support tickets for manual processing.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
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.
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.
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.
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.
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.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with