Issue ryzen1.eq.fra.luxvps.net 23hr 40min ago
Resolved 12hr 25min ago
Resolved: ryzen1.eq.fra.luxvps.net outage
The ryzen1.eq.fra.luxvps.net node went offline again due to a suspected motherboard failure. A technician was sent to the data center with a replacement motherboard, and the previously planned maintenance was brought forward so the motherboard could be replaced the same day.
The technician arrived at 23:36 CET on 06.11.2026 and replaced the motherboard. Despite replacing both the power supplies and the motherboard, the host remained unstable. As we no longer had sufficient confidence in its reliability, we decided to temporarily migrate all affected VMs to an AMD EPYC node.
The automated migration began at 01:12 CET on 07.11.2026, and VMs were started automatically as soon as their individual migrations finished. As of 02:17 CET, all affected VMs have been successfully migrated to the AMD EPYC node and started. If you are still experiencing any issues, please contact our support team.
The original Ryzen Gen4 host will undergo further repairs and extensive testing. Once its stability has been confirmed, all VMs will be migrated back.
As compensation for the disruption, all affected customers will receive a 7-day extension of their service period, free of charge. The extensions will be applied later this evening.
We sincerely apologize for the repeated outages and inconvenience, and thank you for your patience and understanding.
Resolved: ryzen1.eq.fra.luxvps.net outage
The ryzen1.eq.fra.luxvps.net node went offline again due to a suspected motherboard failure. A technician was sent to the data center with a replacement motherboard, and the previously planned maintenance was brought forward so the motherboard could be replaced the same day.
The technician arrived at 23:36 CET on 06.11.2026 and replaced the motherboard. Despite replacing both the power supplies and the motherboard, the host remained unstable. As we no longer had sufficient confidence in its reliability, we decided to temporarily migrate all affected VMs to an AMD EPYC node.
The automated migration began at 01:12 CET on 07.11.2026, and VMs were started automatically as soon as their individual migrations finished. As of 02:17 CET, all affected VMs have been successfully migrated to the AMD EPYC node and started. If you are still experiencing any issues, please contact our support team.
The original Ryzen Gen4 host will undergo further repairs and extensive testing. Once its stability has been confirmed, all VMs will be migrated back.
As compensation for the disruption, all affected customers will receive a 7-day extension of their service period, free of charge. The extensions will be applied later this evening.
We sincerely apologize for the repeated outages and inconvenience, and thank you for your patience and understanding.
Investigating 23hr 40min ago
The ryzen1.eq.fra.luxvps.net node is currently down. Our technician is on the way to the data center to investigate. We’ll post an update when we have more information.
The ryzen1.eq.fra.luxvps.net node is currently down. Our technician is on the way to the data center to investigate. We’ll post an update when we have more information.
Plesk Panel temporarily unavailable on 21 Oct 2026 15:54:52 (UTC+00:00)
Resolved on 22 Oct 2026 09:47:45 (UTC+00:00)
To protect your websites from a newly published critical PHP security vulnerability, we have temporarily closed access to the Plesk control panel. Your websites, email, webmail and FTP keep working normally.
We will reopen the control panel as soon as Plesk releases its security update. If you need anything changed in the meantime (DNS, email accounts, SSL certificates, files), open a support ticket and we’ll take care of it for you.
Thank you for your patience.
To protect your websites from a newly published critical PHP security vulnerability, we have temporarily closed access to the Plesk control panel. Your websites, email, webmail and FTP keep working normally.
We will reopen the control panel as soon as Plesk releases its security update. If you need anything changed in the meantime (DNS, email accounts, SSL certificates, files), open a support ticket and we’ll take care of it for you.
Thank you for your patience.
In progress on 21 Oct 2026 15:54:52 (UTC+00:00)
To protect your websites from a newly published critical PHP security vulnerability, we have temporarily closed access to the Plesk control panel. Your websites, email, webmail and FTP keep working normally.
We will reopen the control panel as soon as Plesk releases its security update. If you need anything changed in the meantime (DNS, email accounts, SSL certificates, files), open a support ticket and we’ll take care of it for you.
Thank you for your patience.
To protect your websites from a newly published critical PHP security vulnerability, we have temporarily closed access to the Plesk control panel. Your websites, email, webmail and FTP keep working normally.
We will reopen the control panel as soon as Plesk releases its security update. If you need anything changed in the meantime (DNS, email accounts, SSL certificates, files), open a support ticket and we’ll take care of it for you.
Thank you for your patience.
Security Updates and Reboots for KVM Host Nodes on 17 Oct 2026 22:57:27 (UTC+00:00)
Resolved
We applied security updates to affected KVM host nodes in response to CVE-2026-99999, a critical Linux kernel vulnerability that may allow a malicious virtual machine to affect its host.
We initially waited for a KernelCare live patch to avoid interrupting customer virtual machines. As a suitable patch did not become available within an acceptable timeframe, we proceeded with kernel updates and reboots. Host nodes were patched and rebooted sequentially to limit the impact.
Customers may have experienced a service interruption of up to approximately 30 minutes while the node hosting their server was updated and restarted.
Customers running their own virtualization stack on dedicated servers, including KVM/QEMU, should assess whether their systems are affected and apply any required updates and reboots themselves. Dedicated servers were not part of this maintenance unless they were operated as part of our managed virtualization infrastructure.
We apologize for the short notice and any inconvenience. Given the potential guest-to-host impact, we could not delay patching further.
We applied security updates to affected KVM host nodes in response to CVE-2026-99999, a critical Linux kernel vulnerability that may allow a malicious virtual machine to affect its host.
We initially waited for a KernelCare live patch to avoid interrupting customer virtual machines. As a suitable patch did not become available within an acceptable timeframe, we proceeded with kernel updates and reboots. Host nodes were patched and rebooted sequentially to limit the impact.
Customers may have experienced a service interruption of up to approximately 30 minutes while the node hosting their server was updated and restarted.
Customers running their own virtualization stack on dedicated servers, including KVM/QEMU, should assess whether their systems are affected and apply any required updates and reboots themselves. Dedicated servers were not part of this maintenance unless they were operated as part of our managed virtualization infrastructure.
We apologize for the short notice and any inconvenience. Given the potential guest-to-host impact, we could not delay patching further.