OVHcloud Bare Metal Cloud Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance

[WAW1][Dedicated Servers] - Rack W17A16 incident notification.

Incident Report for Bare Metal Cloud

Resolved

We would like to inform you that the incident on rack W17A16 has now been resolved.

Here is detail for this incident :
Start time : 02/05/2025 21:38 UTC
End time : 04/05/2025 02:47 UTC
Root Cause : This incident was caused by a network equipment issue.

We thank you for your understanding and patience throughout this incident.
Posted May 04, 2025 - 02:49 UTC

Update

We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Our team is continuing to work on the incident and to restore the service as quickly as possible.
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.
Posted May 04, 2025 - 00:42 UTC

Update

Our teams are mobilised and continue to work to restore service as quickly as possible.

We will keep you updated on progress and resolution.
We apologise for any inconvenience caused and thank you for your patience.
Posted May 03, 2025 - 11:36 UTC

Update

The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

As soon as the situation evolves or the incident is resolved, we will keep you informed.

Thank you for your understanding
Posted May 03, 2025 - 02:13 UTC

Identified

We have determined the origin of the incident affecting our Dedicated Servers offer in the specific rack W17A16 .

Here are some supplementary details :
Start time : 02/05/2025 21:38 UTC
Impacted Service(s) : Servers in the specified rack are no longer able to access the vRack network.
Customers Impact : Customers do not currently have access to their vRack network on servers in the specified rack.
Root Cause : This incident is caused by 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
Posted May 02, 2025 - 21:58 UTC

Update

We have determined the origin of the incident affecting our Dedicated Servers offer in the specific rack W17A16 .

Here are some supplementary details :
Start time : 02/05/2025 21:38 UTC
Impacted Service(s) : Servers in the specified rack are no longer able to access the vRack network.
Customers Impact : Customers do not currently have access to their vRack network on servers in the specified rack.
Root Cause : This incident is caused by 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.
Posted May 02, 2025 - 21:56 UTC

Investigating

We are currently experiencing an event affecting our Dedicated Servers offer in the specific rack W17A16
Start time : 02/05/2025 21:38 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.
Posted May 02, 2025 - 21:54 UTC
This incident affected: Dedicated Servers || Network (WAW).