OVHcloud Bare Metal Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
[SGP2][Dedicated Servers] - Racks SGP0201C03A/SGP0201C03B/SGP0201C03C 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 : 16/03/2026 12:23 UTC
End time : 16/03/2026 16:30 UTC
Root Cause : This incident was caused by a cooling system issue.
We apologize for any inconvenience caused and appreciate your understanding.
Start time : 16/03/2026 12:23 UTC
End time : 16/03/2026 16:30 UTC
Root Cause : This incident was caused by a cooling system issue.
We apologize for any inconvenience caused and appreciate your understanding.
Update
We have new informations regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : The IPMI service is now operational on the servers in the racks SGP0201C03A/SGP0201C03B/SGP0201C03C.
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 : The IPMI service is now operational on the servers in the racks SGP0201C03A/SGP0201C03B/SGP0201C03C.
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 investigating an incident affecting our Dedicated Servers offer in the racks SGP0201C03A/SGP0201C03B/SGP0201C03C.
Here are some supplementary details :
Start time : 16/03/2026 12:23 UTC
Impacted Service(s) : Some servers in rack SGP0201C03A are no longer able to access the vRack network, except for those configured in LACP. Servers located in racks SGP0201C03A/SGP0201C03B/SGP0201C03C are no longer reachable through their IPMI interfaces.
Customers Impact : Some customers are temporarily unable to access or use their servers via the vRack network if LACP has not been configured in rack SGP0201C03A. In addition, they are unable to access their servers through the IPMI interface in racks SGP0201C03A/SGP0201C03B/SGP0201C03C.
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 : 16/03/2026 12:23 UTC
Impacted Service(s) : Some servers in rack SGP0201C03A are no longer able to access the vRack network, except for those configured in LACP. Servers located in racks SGP0201C03A/SGP0201C03B/SGP0201C03C are no longer reachable through their IPMI interfaces.
Customers Impact : Some customers are temporarily unable to access or use their servers via the vRack network if LACP has not been configured in rack SGP0201C03A. In addition, they are unable to access their servers through the IPMI interface in racks SGP0201C03A/SGP0201C03B/SGP0201C03C.
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 (SGP).