Updates
Dear Customers,
We have successfully completed the emergency maintenance across our KVM infrastructure. We want to provide clear technical context on why this intervention happened on such short notice.
A critical vulnerability in the Linux KVM hypervisor was publicly disclosed, which could allow malicious actors to trigger guest to host escapes or crash host nodes entirely. You can read the full technical disclosure here: https://thehackernews.com/2026/07/16-year-old-linux-kvm-flaw-lets-guest.html
Protecting your data integrity and securing our host infrastructure is our absolute priority. Because of the severity of this exploit, we could not hesitate in deploying the mitigation. We specifically executed this rollout during the night to keep the noticeable impact on your active services as low as possible.
During the rollout, we issued graceful shutdown signals to all virtual machines to allow operating systems to halt cleanly.
As previously announced, mitigating this issue generally required changing the CPU type from "Host" to a standard profile. For the time being, Nested Virtualization is deactivated as a precaution. We are closely monitoring the situation for upstream kernel patches. Once a reliable patch is released and tested, our goal is to deploy it and we aim to offer Nested Virtualization upon request again.
We apologize for the lack of advance notice and any disruptions this emergency patch caused. If your server has not recovered as expected or you are facing any subsequent issues, please open a support ticket and we will assist you as soon as possible.
Clusters Xeon EQ7,Epyc,Ryzen Gen3,Ryzen Gen4 are done.
Dear Customers,
Your KVM server will undergo a brief reboot during the night. This is due to a necessary security mitigation at the hypervisor level to ensure continued system integrity. The downtime will last between 30 seconds and one minute. Please be assured that this will remain a single short interruption, and no further downtimes are foreseen at this time.
As part of this mitigation, we must change the CPU type of your virtual machines from "Host" to a standard compatible profile. As a precautionary measure, Nested Virtualization (running a VM inside a VM) is now deactivated.
If an official kernel patch becomes available in the future, we will apply it and can re-enable Nested Virtualization for your server upon request.
We apologize for the short downtime and appreciate your understanding.