OVHcloud Private Cloud Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
[RBX8][VMware Private Cloud] - VMware Private Cloud incident notification
Incident
Report for Hosted Private Cloud
Resolved
We would like to inform you that the incident on our VMware Private Cloud offering, have been resolved
Start Time : 14/04/2025 12:30 UTC
End Time : 15/04/2025 14:59 UTC
Root cause : This incident is caused by an electrical equipment issue.
We thank you for your understanding and patience throughout this incident
Start Time : 14/04/2025 12:30 UTC
End Time : 15/04/2025 14:59 UTC
Root cause : This incident is caused by an electrical equipment issue.
We thank you for your understanding and patience throughout this incident
Update
The service impacted by this incident has been reachable and stable since 14/04/2025 14:59 UTC.
We continue to monitor the situation to ensure the state of the service. No further impact have observed since last update.
If you’re experiencing an impact nonetheless, here is the advised troubleshooting procedure :
Troubleshooting Reminder : For customers that are still experiencing issues accessing their Virtual Machines (VMs), please reboot the impacted VMs to resolve the issue. To ensure data consistency, we recommend running the FSCK tool.
Ongoing Actions : Our technical teams continue to actively monitor the situation to ensure the service remains stable and to quickly address any potential issues that may arise.
We apologize for any inconvenience caused and appreciate your understanding.
We continue to monitor the situation to ensure the state of the service. No further impact have observed since last update.
If you’re experiencing an impact nonetheless, here is the advised troubleshooting procedure :
Troubleshooting Reminder : For customers that are still experiencing issues accessing their Virtual Machines (VMs), please reboot the impacted VMs to resolve the issue. To ensure data consistency, we recommend running the FSCK tool.
Ongoing Actions : Our technical teams continue to actively monitor the situation to ensure the service remains stable and to quickly address any potential issues that may arise.
We apologize for any inconvenience caused and appreciate your understanding.
Monitoring
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation:
Update : The service is back to nominal state.
Customers who are still unable to access their VMs, need to reboot their impacted VMs.
To check data consistency we recommend that you use FSCK tool.
Ongoing Actions :Our technical teams are currently monitoring the situation.
We apologize for any inconvenience caused and appreciate your understanding.
Please find below an update on the situation:
Update : The service is back to nominal state.
Customers who are still unable to access their VMs, need to reboot their impacted VMs.
To check data consistency we recommend that you use FSCK tool.
Ongoing Actions :Our technical teams are currently monitoring the situation.
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 : The majority of the VMs are now operational.
Customers who are still unable to access their VMs, need to reboot their impacted VMs.
To check data consistency we recommend that you use FSCK tool.
Ongoing Actions : The incident has been identified and our teams are mobilized 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 majority of the VMs are now operational.
Customers who are still unable to access their VMs, need to reboot their impacted VMs.
To check data consistency we recommend that you use FSCK tool.
Ongoing Actions : The incident has been identified and our teams are mobilized 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 : The majority of the VMs are now operational.
Customers who are still unable to access their VMs, need to reboot their impacted VMs.
Ongoing Actions : The incident has been identified and our teams are mobilized 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 majority of the VMs are now operational.
Customers who are still unable to access their VMs, need to reboot their impacted VMs.
Ongoing Actions : The incident has been identified and our teams are mobilized 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 VMware Private Cloud offer on the rack R821L17 in the region RBX2B.
Here are some supplementary details :
Start time : 14/04/2025 12:30 UTC
Impacted Service(s) : Some datastores are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access and use their VMs located in rack R821L17.
Root Cause : This incident is caused by an electrical 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.
Here are some supplementary details :
Start time : 14/04/2025 12:30 UTC
Impacted Service(s) : Some datastores are temporarily unavailable.
Customers Impact : Customers are temporarily unable to access and use their VMs located in rack R821L17.
Root Cause : This incident is caused by an electrical 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.
Investigating
We are currently experiencing an incident affecting our VMware Private Cloud offering, which is causing temporary availability issues in the region RBX2B.
Here is detail for this incident :
Start time : 14/04/2025 12:30 UTC
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
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 : 14/04/2025 12:30 UTC
Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
This incident affected: Managed VMware Cloud Director || RBX (Storage).