We are pleased to inform you that the incident affecting our Managed VMware vSphere has been resolved.
Start time : 26/02/2026 05:17 UTC End time : 26/02/2026 17:00 UTC Root Cause : This incident was caused by a cooling system issue.
We apologize for any inconvenience caused and appreciate your understanding.
Posted Feb 26, 2026 - 17:04 UTC
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : Most hosts are now operational again on R805L26 and R805L27. Ongoing Actions : Our teams are still working to restore service on R805L25 and the remaining hosts that are still down.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Posted Feb 26, 2026 - 08:20 UTC
Identified
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Managed VMware vSphere offer on racks R805L25/R805L26/R805L27.
Here are some supplementary details :
Start time : 26/02/2026 05:17 UTC Impacted Service(s) : Some hosts are temporarily unavailable. 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.
Posted Feb 26, 2026 - 05:38 UTC
Investigating
We are currently investigating an incident affecting our Managed VMware vSphere offering, which is causing temporary availability issue in racks R805L25/R805L26/R805L27.
Here are some supplementary details :
Start time : 26/02/2026 05:17 UTC Impacted Service(s) : Some hosts are temporarily unavailable. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.
We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.
Posted Feb 26, 2026 - 05:26 UTC
This incident affected: Managed VMware vSphere || RBX (Compute).