OVHcloud Bare Metal Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
[WAW1][Dedicated Servers] - Racks W17A13/W17A14 incident notification
Incident
Report for Bare Metal Cloud
Resolved
We are pleased to inform you that the incident affecting our Dedicated Servers has been resolved.
Start time : 01/11/2025 01:30 UTC
End time : 01/11/2025 07:57 UTC
Root Cause : This incident is caused by a cooling system issue.
We apologize for any inconvenience caused and appreciate your understanding.
Start time : 01/11/2025 01:30 UTC
End time : 01/11/2025 07:57 UTC
Root Cause : This incident is caused by a cooling system issue.
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 : Most servers in racks W17A13 and W17A14 are now operational. Most of the servers in rack W17A13 can now be accessed via the public network.
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 : Most servers in racks W17A13 and W17A14 are now operational. Most of the servers in rack W17A13 can now be accessed via the public network.
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 servers in racks W17A13 and W17A14 are now operational.
Customers are temporarily unable to access their servers via public network located in rack W17A13 due to a network equipment 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.
Please find below an update on the situation:
Update : All servers in racks W17A13 and W17A14 are now operational.
Customers are temporarily unable to access their servers via public network located in rack W17A13 due to a network equipment 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.
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : All servers in rack W17A13 and a significant number of servers in rack W17A14 are now operational.
Customers are temporarily unable to access their servers via public network located in rack W17A13 due to a network equipment 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.
Please find below an update on the situation:
Update : All servers in rack W17A13 and a significant number of servers in rack W17A14 are now operational.
Customers are temporarily unable to access their servers via public network located in rack W17A13 due to a network equipment 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.
Identified
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Dedicated Servers offer on the specific racks W17A13 and W17A14.
Here are some supplementary details :
Start time : 01/11/2025 01:30 UTC
Impacted Service(s) : All servers in the racks W17A13 and W17A14 are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their servers located on 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 are some supplementary details :
Start time : 01/11/2025 01:30 UTC
Impacted Service(s) : All servers in the racks W17A13 and W17A14 are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access their servers located on 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 (WAW) and Dedicated Servers || Network (WAW).