OVHcloud Bare Metal Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
[RBX4][Dedicated Servers] - Multiple Racks incident notification
Incident
Report for Bare Metal Cloud
Resolved
We would like to inform you that the incident on our Dedicated Servers offer on the specific racks has now been resolved.
Here is detail for this incident :
Start time : 10/07/2025 09:42 UTC
End time : 10/07/2025 20:44 UTC
Root Cause : This incident was caused by a cooling system issue.
We thank you for your understanding and patience throughout this incident.
Here is detail for this incident :
Start time : 10/07/2025 09:42 UTC
End time : 10/07/2025 20:44 UTC
Root Cause : This incident was caused by a cooling system issue.
We thank you for your understanding and patience throughout this incident.
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : All of servers in racks 55B17 - 53B17- 51B17 - 55B16 and 55B18 are now operational.
A significant number of servers in racks 54B18 are now operational.
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.
Please find below an update on the situation:
Update : All of servers in racks 55B17 - 53B17- 51B17 - 55B16 and 55B18 are now operational.
A significant number of servers in racks 54B18 are now operational.
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.
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : All of servers in racks 51B17 - 55B16 and 55B18 are now operational.
A significant number of servers in racks 53B17, 54B18, and 55B17 are now operational.
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.
Please find below an update on the situation:
Update : All of servers in racks 51B17 - 55B16 and 55B18 are now operational.
A significant number of servers in racks 53B17, 54B18, and 55B17 are now operational.
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.
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : Since 10:43 UTC, vRack is available again for servers in rack 54B18.
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.
Please find below an update on the situation:
Update : Since 10:43 UTC, vRack is available again for servers in rack 54B18.
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 determined the origin of the incident affecting our Dedicated Servers offer on the specific racks.
Here is detail for this incident :
Start time : 10/07/2025 09:42 UTC
Impacted Service(s) : Some servers in racks 51B17, 52B16, 52B17, 53B17, 54B18, 55B16, 55B17 and 55B18 are temporarily unavailable.
Also, vRack is temporarily unavailable for servers in rack 54B18.
Customers Impact : Some customers are temporarily unable to access and use their servers located in the specified racks.
Root Cause : This incident is caused by a cooling system issue.
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.
Here is detail for this incident :
Start time : 10/07/2025 09:42 UTC
Impacted Service(s) : Some servers in racks 51B17, 52B16, 52B17, 53B17, 54B18, 55B16, 55B17 and 55B18 are temporarily unavailable.
Also, vRack is temporarily unavailable for servers in rack 54B18.
Customers Impact : Some customers are temporarily unable to access and use their servers located in the specified racks.
Root Cause : This incident is caused by a cooling system issue.
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.
This incident affected: Dedicated Servers || Global Infrastructure (RBX).