Update - • We have temporarily disabled access to the Plesk control panels again. Further verification showed that the separate PHP runtime used by Plesk itself still requires an additional vendor security update.
• This restriction affects Plesk access only. The websites restored earlier remain online.
• We understand that you need panel access to manage your services, particularly to make the PHP version changes described in our earlier updates. We are sorry for the additional disruption. We currently have no ETA for restoring access. The panels will remain unavailable until we can apply and verify the required security update.
• Managed Servers: You do not need panel access for this. Our support team (hi@dataforest.net) can still switch all domains on your server that use outdated PHP versions to PHP 8.2, 8.3, 8.4 or 8.5.

Oct 21, 2026 - 22:34 CEST
Update - • All web hosting and managed servers were brought back online between 18:15 and 18:30 CEST.
• Managed Servers: As previously explained, we have not changed any PHP versions on managed servers. If your website still uses an unsupported PHP version, please select a supported version in Plesk. Our support team can also switch all domains on your server that still use outdated PHP versions to PHP 8.2, 8.3, 8.4 or 8.5. Websites already using a supported PHP version should be accessible again. If this is not the case, or if you are experiencing other unexpected issues, please contact our support team.
• Webhosting: If your application is compatible with PHP 8.2 or later but you are still experiencing issues, please contact our support team.
• For all other cases related to this incident, including questions already answered in this post, please refrain from contacting our support team. This helps prevent support overload and keeps our team available for customers who need individual assistance.
• Updates for managed mailcow instances became available a few minutes ago, and we are already deploying them. Brief service interruptions may occur during the rollout.

Oct 21, 2026 - 20:13 CEST
Update - We have temporarily disabled some payment methods in the Avoro customer area because external licensing and payment services are unavailable for the same reasons. These outages are beyond our control. We will reactivate the affected payment methods as soon as the external services are restored.
Oct 21, 2026 - 18:37 CEST
Update - • All managed server and web hosting systems have been patched and updated. The rollout took some time due to overloaded download mirrors.
• The majority of our own infrastructure, including our customer portals, is back online. Some non-critical or legacy services are not.
• Plesk panels are available again, too.
• We have decided to take a different approach depending on the product:
• Managed Servers: Websites configured to use unsupported PHP versions will not be automatically switched to PHP 8.5 to avoid compatibility issues. Instead, unsupported PHP versions will remain disabled, and affected websites will display an error page with HTTP status code 503 (Service Unavailable). Customers must manually select a supported PHP version in Plesk.
• Webhosting: Websites configured to use unsupported PHP versions have been switched to PHP 8.5. Supported PHP versions down to 8.2 remain available for selection.
• We have already started bringing our web hosting and managed servers back online. All websites running PHP 8.2 or later should be available again within the next 15-60 minutes.
• The PHP team has provided minimal security backports for the end-of-life (EOL) versions PHP 7.4, 8.0 and 8.1 as a one-time exception. We are monitoring the situation closely, but please do not rely on these becoming available for our systems, especially since these are not yet available through Plesk or the relevant Linux distributions. Furthermore, these PHP versions had already reached end of life before and should no longer have been in use. For websites still configured to use an unsupported PHP version, switching to a supported version is currently the only available way to restore service on our systems.

Oct 21, 2026 - 18:22 CEST
Update - First exploitations are seen in the wild. We have shut down all PHP services on managed servers and web hosting servers. We understand that this is a drastic measure. It is necessary to protect your data.

We are deploying PHP updates for supported versions across our infrastructure which were released a few minutes ago. Before bringing back online the systems, we will disable unsupported PHP versions by switching the affected websites to PHP 8.5. You will then be able to switch back as far as PHP 8.2, but you will no longer be able to select an unsupported version.

If you are running PHP applications on an unmanaged server, shut them down now until you have updated.

Emergency support is available via hi@dataforest.net.

Oct 21, 2026 - 15:59 CEST
Update - • Updated: Title and sources
• Specified: dataforest's own infrastructure
• Please refrain from individual requests to our support about the situation. You find our suggested actions in this post. Migrate your websites to new (supported) PHP versions as described below or simply shut them down until PHP updates are released as a precautionary measure. The first governments already did so with their websites.
• Due to the urgency of the situation, we have sent out a newsletter to all customers.

Oct 21, 2026 - 15:32 CEST
Identified - We would like to inform you about two critical security vulnerabilities in the PHP scripting language. Please read this post carefully and in full. We ask for your understanding that information is still limited, the situation may change at any time, and this post will therefore be updated continuously. Please subscribe to our status page to receive updates and check this post regularly.

Summary

According to current assessments, these vulnerabilities allow remote code execution in all PHP versions from version 5 onwards. In simple terms, attackers can exploit them to execute arbitrary code in the context of the affected PHP application. The application only needs to be accessible over the internet. With nearly 70% of all websites using PHP, the potential impact is substantial. Of particular concern is that only PHP 8.5, 8.4, 8.3 and 8.2 still receive security updates. Websites running older PHP versions that are no longer supported should therefore be migrated to a current version immediately.

We do not want to cause panic: our specialists convened immediately, developed an action plan and have already begun implementing it. All departments are ready to respond. Nevertheless, website operators and server administrators need to remain alert and act quickly. Further information on our response and our recommendations is provided below.

Details of the vulnerabilities were originally scheduled to be published on 22.10.2026 at 17:00 CEST, after the corresponding security updates had been made available. However, information was leaked by unknown parties a few hours ago. The PHP security team has therefore announced that the release has been brought forward and is imminent.

Managed servers and web hosting

We have begun disabling outdated PHP handlers. This means that only PHP versions that still receive security updates can be selected. We strongly urge you to switch your websites to one of these versions immediately. Where necessary, isolate outdated applications that cannot be migrated immediately from the internet, then migrate them to newer software without leaving them exposed.

Please note: As soon as we become aware of a publicly available and therefore actively exploited exploit, we will immediately disable unsupported PHP versions across all managed servers and web hosting servers by switching the affected websites to PHP 8.5. You would then be able to switch back as far as PHP 8.2, but would no longer be able to select an unsupported version. We understand that this would be a drastic step, but we must consider it to protect your data and that of your customers.

For supported PHP versions, we expect updates over the coming days and will install them as soon as they become available. At present, we cannot predict whether exploits will become public and be used before then. Please assess whether you wish to isolate your PHP-powered websites from the internet until updates are available.

Unmanaged (self-managed) servers

Our recommendation: migrate outdated PHP applications to a supported PHP version immediately. Update your PHP installation as soon as updates become available for your system. If your operating system no longer receives updates, upgrade it immediately. Isolate applications from the internet if they cannot be migrated promptly.

Outlook

Once sufficient technical details are available, we will also assess whether the attack vectors can be mitigated at the web server level (for example, through a Web Application Firewall enabled by default on Plesk servers) or by other means. Until we know more, however, we must assume that running a supported PHP version and installing the corresponding updates is the only option.

dataforest's own infrastructure

- We have decided to shut down particularly critical systems as a precaution until the situation becomes clearer – especially those that handle customer data or have extensive internal permissions. This may temporarily limit certain product and server management functions. During this time, you can ask our support team at hi@dataforest.net to carry out the corresponding actions for you at any time.

- Over the coming hours and days, we reserve the right to perform maintenance on any of our customer portals, temporarily restrict access to them, or shut down legacy sites permanently without further notice.

Sources

https://www.php.net/archive/2026.php
https://cert.europa.eu/publications/security-advisories/2026-018/
https://watchtowr.com/intelligence/php-cve-2026-109618-faq/
https://www.heise.de/en/news/Critical-PHP-updates-on-Oct-21-fix-code-injection-vulnerabilities-11495177.html
https://www.bsi.bund.de/DE/Service-Navi/Presse/Pressemitteilungen/Presse2026/261021_PHP-kritische-Schwachstelle.html
https://www.tagesschau.de/wirtschaft/technologie/it-sicherheit-php-luecke-100.html

Oct 21, 2026 - 03:55 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 12, 2026 - 08:00 CEST
Scheduled - Start: 12.10.2026, 08:00 CEST
End: 23.10.2026, 17:00 CEST

Power infrastructure upgrades will be carried out at FC-FRA4 across two phases. The work is intended to improve redundancy and operational stability while providing additional capacity for future growth. No downtime is planned for connected systems.

From 12.10.2026 to 16.10.2026, the power feeds of distribution systems A and B will be modified to improve selectivity and operational safety. The work will be performed sequentially, with only one power path being worked on at a time. During each respective phase, the affected power path will be supplied by the datacenter's diesel generator system, while UPS protection remains active throughout generator operation.

As this phase involves switching and work on the active power infrastructure, a small residual risk remains. In the (unlikely and unexpected) event of a disruption affecting the respective path, some rack feeds will become unavailable.

From 19.10.2026 to 23.10.2026, additional electrical supply lines will be installed, tested and commissioned to expand the site's power infrastructure and provide additional capacity.

We will provide an update should any unexpected impact occur.

Oct 12, 2026 08:00 - Oct 23, 2026 17:00 CEST
dataforest Network Operational
Edge Network (affects all locations) Operational
DDoS Protection (affects all locations) Operational
Dedicated Servers (EQX-FR4 & DRT-FRA8) Operational
Datacenter MC-FRA01 Partial Outage
Datacenter Core Routing & Switching Operational
Ceph Cluster Operational
Virtual Servers Partial Outage
Dedicated Servers Operational
Plesk Web Hosting Partial Outage
TeamSpeak3 Servers Operational
Network Storage Operational
Facilites Operational
Datacenter FC-FRA4 Under Maintenance
Datacenter Core Routing & Switching Operational
Dedicated Servers Operational
Facilites Under Maintenance
General Services Partial Outage
Avoro CP & Support Partial Outage
PHP-Friends CRM & Support Partial Outage
Hotline Operational
Dedicated Control Panel Operational
IPMI VPN Operational
DDoS Manager Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Oct 22, 2026

No incidents reported today.

Oct 21, 2026

Completed - The scheduled maintenance has been completed.
Oct 21, 13:38 CEST
Verifying - All host systems have been successfully rebooted, and the maintenance is complete. We will keep this notice open for the next few hours to ensure the final update remains visible.

Thank you for your patience and for the understanding shown by the vast majority of our customers throughout this maintenance. The reboots were necessary for the security patch to take effect. We completed the rollout before a public exploit was available. This timing was critically important to protecting your systems and data.

Oct 20, 22:19 CEST
Update - The reboot of the host vps-017, carried out at 15:15, took longer than expected. The host came back online at 15:35, and its VMs have been starting up one by one since then. We expect all VMs on this host to be up and running by 15:50. We are continuing with the remaining host reboots.
Oct 20, 15:33 CEST
Update - The reboot of the host epyc9754-4, carried out at 14:32, took longer than expected. It is back online since 14:55. We are continuing with the remaining host reboots.
Oct 20, 14:51 CEST
Update - We are still rebooting the remaining Avoro hosts and have not completed the maintenance. Check your server's uptime: if we have already rebooted it during this maintenance, no further reboot is needed. Otherwise, its reboot is still pending. See the initial maintenance notice for details.
Oct 19, 23:56 CEST
Update - We have resolved the issues with epyc9374f-2 at 18:17 (total downtime: 30 minutes), all VMs on this node are back online.
Oct 19, 18:21 CEST
Update - We are currently experiencing unexpected issues with the node epyc9374f-2 which was rebooted at 17:47. This also affects ts12.avoro.eu as well as the VPS management in the Avoro customer area. We are working on a fix with the highest priority. Since this is a known issue that is being actively handled, please refrain from contacting support regarding these nodes. Keep an eye on this status page for the latest information.
Oct 19, 18:09 CEST
Update - All dataforest cloud nodes and all legacy PHP-Friends hosts have been patched and rebooted with only 5 to 10 minutes of downtime.
The Avoro virtualization cluster requires additional preparation that was not anticipated, so no reboots have taken place there yet. We are therefore extending the maintenance window by two days for Avoro only. The first reboots will begin in 10-12 hours.

Oct 19, 01:15 CEST
Update - All dataforest cloud nodes and the majority of legacy PHP-Friends hosts have already been patched and rebooted. We are well ahead of schedule and will pause maintenance overnight. Patching and reboots will resume in the morning.
Oct 18, 00:37 CEST
Update - 25% of VMs have already been rebooted. You can check your system's uptime: if it was rebooted (by dataforest) recently, the maintenance for this VM has been completed. If not, the reboot is still pending.
Oct 17, 22:34 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 17, 16:30 CEST
Scheduled - Updated maintenance schedule:
Start: 17.10.2026 16:30 CEST
End: 21.10.2026 23:59 CEST

A critical security vulnerability known as "PwnEscape" has been discovered in KVM, the virtualization technology powering our infrastructure. This flaw potentially affects all virtual servers across our infrastructure. Over the past 24 hours, our team has analyzed the threat and developed an immediate mitigation plan.

This is one of the most severe vulnerabilities reported in KVM to date. While there are currently no public exploits available to compromise host systems, we expect this to change imminently. To ensure the security of our infrastructure and our customers, we need to carry out this maintenance without unnecessary delays.

Affected products
This maintenance applies to every type of virtual server in our infrastructure, including:
- Seeds in the dataforest cloud
- Virtualized Avoro products (VPS, Rootserver, Power Rootserver, NVMe vServer, Compute vServer, Cloud Server)
- Every PHP-Friends vServer; both managed and unmanaged
- Our Plesk web hosting systems and TeamSpeak 3 servers (as these are hosted on the same virtualization platform)

What we are doing
Our engineers will work in multiple shifts to apply a security patch to all host systems, which requires a reboot of all virtual servers. The maintenance will begin in approximately 2 hours and is expected to take up to 48 hours. Given the scale of the operation, we are unfortunately unable to arrange individual maintenance windows. Should we need to adjust the schedule, we will update this post.

Expected impact
- We expect a brief downtime of 5 to 15 minutes per virtual server. If your server is unreachable for more than 15 minutes, please check this post for updates regarding potential host-specific issues. If there are no known issues listed, please contact our support.
- For unmanaged server customers: Ensure your VM is reboot-safe. Configure critical software to autostart on boot and terminate cleanly upon a shutdown signal from the host. Please understand that we cannot take responsibility for the internal configuration of unmanaged servers.
- For managed, webhosting, and TeamSpeak 3 customers: You do not need to take any action. Our team manages the configuration and safe reboot of your services automatically.

Oct 17, 14:43 CEST
Completed - We have postponed this maintenance to prioritize our response to the critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 (https://status.dataforest.net/incidents/tnwzr68wvgdw). Our teams will focus fully on this work over the coming hours and days.
Oct 21, 13:38 CEST
Scheduled - We will update the software of the switches that provide network connectivity to the dedicated server rack(s) mentioned below at MC-FRA01 to resolve known bugs and ensure long-term stability. After the update, a reboot is required.

Expected impact
During the maintenance window, there will be a network interruption during each switch reboot. The reboot is expected to take up to 20 minutes per switch.

- Servers with only one uplink will lose network connectivity during that reboot. Connectivity should recover automatically once the switch is back online.
- Servers with two uplinks are designed to remain reachable during this maintenance, as one physical uplink will remain available while the other switch is rebooting.
- For servers with two uplinks, correct LACP configuration on the customer side is always required. Two physical uplinks only provide redundancy if they are configured as one LACP channel. If LACP is missing or incorrectly configured on the customer side, the server will become unreachable during the maintenance, even though redundant uplinks are physically available.

dataforest does not verify customer-side LACP configuration for unmanaged dedicated servers. Customers are responsible for ensuring that both provided uplinks are correctly configured and operational.

Affected rack(s)
BD09

How to check if you are affected
In our control panel at https://dedicated.dataforest.cloud, open the server and check "Statistics". If one of your ports shows a description containing one of the rack identifiers listed above, your server is part of the maintenance scope.

You can see whether your server has one or two uplinks in your contract or product details. If two uplinks are included, LACP must be configured and actively used on your side.

We will complete the work as quickly as possible and aim to keep the interruption to the minimum stated above. Thank you for your understanding.

Sep 29, 17:06 CEST

Oct 20, 2026

Oct 19, 2026

Completed - The scheduled maintenance has been completed.
Oct 19, 16:15 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 19, 15:15 CEST
Scheduled - Start: 19.10.2026, 15:15 CEST
End: 19.10.2026, 16:15 CEST

We will carry out maintenance on our DDoS protection infrastructure.

What we are doing
We will deploy software updates to our redundant scrubbing cluster. Filter appliances will be taken out of production and updated one by one to ensure mitigation capacity is always sufficient. After each update, functionality will be verified before we move on to the next filter.

Expected impact
No customer impact is expected, but it cannot be ruled out entirely. Idle (inactive) connections/sessions may time out; active ones should not, as they are synchronized during the startup of a new software release. If you notice anything unusual, such as timeouts of active sessions or the inability to connect to your server, please contact our support.

Affected customers
All IP prefixes routed through our DDoS protection (which is the default).

Fallback plan
Should the update fail and cause issues, we will disconnect the respective filters within a few seconds.

Oct 17, 16:24 CEST

Oct 18, 2026

Oct 17, 2026

Completed - The scheduled maintenance has been completed.
Oct 17, 01:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 16, 22:00 CEST
Scheduled - Start: 16.10.2026, 22:00 CEST
End: 17.10.2026, 01:00 CEST

We need to carry out maintenance on the host system vnode14 which is containing PHP-Friends HDD VMs. The VMs will be migrated to other (identical) host systems which involves a short downtime (depending on the disk size of the VM, about 10 minutes per 30 GB). Customers may check in our control panel (SolusVM) if they have any VMs running on vnode14.

To minimize the impact for affected customers, we migrate one VM after another and we will do it over night only (22:00 CEST - 01:00 CEST).

Please make always sure that your VM is configured to be "reboot resistant", so that all software you need starts at boot time and is stopped cleanly when the host system sends an ACPI shutdown signal.

Oct 9, 23:30 CEST

Oct 16, 2026

Oct 15, 2026

Completed - The scheduled maintenance has been completed.
Oct 15, 15:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 13:00 CEST
Scheduled - Start: 15.10.2026, 13:00 CEST
End: 15.10.2026, 15:00 CEST

We will replace the switches of the dedicated server racks X12 and X13 at FC-FRA4 with new hardware, following the issues encountered during previous maintenance work on these switches. Affected servers will experience a brief network interruption while being moved to the new switches.

Affected rack(s)
X12
X13

If your server is not located in one of these racks, you are not affected and no action is required.

How to check if you are affected
In our control panel at https://dedicated.dataforest.cloud, open the server and check "Statistics". If one of your ports shows a description containing one of the rack identifiers listed above, your server is part of the maintenance scope.

You can see whether your server has one or two uplinks in your contract or product details. If two uplinks are included, LACP must be configured and actively used on your side.

Expected impact
During the maintenance window, all servers in the affected racks will be moved to the new switches. Servers will be re-cabled one after another, uplink by uplink. The servers themselves will not be rebooted.

- Servers with only one uplink will lose network connectivity while being re-cabled, for up to 30 seconds. Connectivity should recover automatically once the server is connected to the new switch.
- Servers with two uplinks will experience a considerably shorter interruption, as one physical uplink remains active while the other one is being moved to the new switch.
- For servers with two uplinks, correct LACP configuration on the customer side is always required. Two physical uplinks only provide redundancy if they are configured as one LACP channel. If LACP is missing or incorrectly configured on the customer side, the server will experience an interruption of up to 30 seconds, even though redundant uplinks are physically available.

We will complete the work as quickly as possible and aim to keep the interruption to the minimum stated above. Thank you for your understanding.

Oct 2, 19:06 CEST
Completed - The second switch was rebooted between 00:26 and 00:35 without any issues. The maintenance has now been completed successfully.
Oct 15, 00:41 CEST
Update - During the reboot of the first switch at 00:10, our vnode034 host (PHP-Friends vServer) and the hypervisor hosting avoro.eu, php-friends.de and their respective customer portals unexpectedly went offline. Both recovered at 00:19, once the switch had completed its reboot. We will investigate the redundancy failure after the maintenance is complete. We apologize for the inconvenience.
Oct 15, 00:24 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 15, 00:00 CEST
Scheduled - Start: 15.10.2026, 00:00 CEST
End: 15.10.2026, 01:00 CEST

We will update the software of the switches that provide network connectivity to the dedicated server rack(s) mentioned below at MC-FRA01 to resolve known bugs and ensure long-term stability. After the update, a reboot is required.

Expected impact
During the maintenance window, there will be a network interruption during each switch reboot. The reboot is expected to take up to 20 minutes per switch.

- Servers with only one uplink will lose network connectivity during that reboot. Connectivity should recover automatically once the switch is back online.
- Servers with two uplinks are designed to remain reachable during this maintenance, as one physical uplink will remain available while the other switch is rebooting.
- For servers with two uplinks, correct LACP configuration on the customer side is always required. Two physical uplinks only provide redundancy if they are configured as one LACP channel. If LACP is missing or incorrectly configured on the customer side, the server will become unreachable during the maintenance, even though redundant uplinks are physically available.

dataforest does not verify customer-side LACP configuration for unmanaged dedicated servers. Customers are responsible for ensuring that both provided uplinks are correctly configured and operational.

Affected rack(s)
AZ07

How to check if you are affected
In our control panel at https://dedicated.dataforest.cloud, open the server and check "Statistics". If one of your ports shows a description containing one of the rack identifiers listed above, your server is part of the maintenance scope.

You can see whether your server has one or two uplinks in your contract or product details. If two uplinks are included, LACP must be configured and actively used on your side.

We will complete the work as quickly as possible and aim to keep the interruption to the minimum stated above. Thank you for your understanding.

Sep 28, 23:57 CEST

Oct 14, 2026

Completed - The scheduled maintenance has been completed.
Oct 14, 17:35 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 14, 16:00 CEST
Scheduled - Start: 14.10.2026, 16:00 CEST
End: 14.10.2026, 19:00 CEST

We will carry out maintenance on our DDoS protection infrastructure.

What we are doing
We will deploy software updates to our redundant scrubbing cluster. Filter appliances will be taken out of production and updated one by one to ensure mitigation capacity is always sufficient. After each update, functionality will be verified before we move on to the next filter.

Expected impact
No customer impact is expected, but it cannot be ruled out entirely. Idle (inactive) connections/sessions may time out; active ones should not, as they are synchronized during the startup of a new software release. If you notice anything unusual, such as timeouts of active sessions or the inability to connect to your server, please contact our support.

Affected customers
All IP prefixes routed through our DDoS protection (which is the default).

Fallback plan
Should the update fail and cause issues, we will disconnect the respective filters within a few seconds.

Oct 13, 15:02 CEST

Oct 13, 2026

No incidents reported.

Oct 12, 2026

Unresolved incident: [FC-FRA4] Power Infrastructure Upgrades.

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

Completed - The scheduled maintenance has been completed.
Oct 9, 17:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 9, 16:00 CEST
Scheduled - Start: 09.10.2026, 16:00 CEST
End: 09.10.2026, 17:00 CEST

We will carry out maintenance on our DDoS protection infrastructure.

What we are doing
We will deploy software updates to our redundant scrubbing cluster. Filter appliances will be taken out of production and updated one by one to ensure mitigation capacity is always sufficient. After each update, functionality will be verified before we move on to the next filter.

Expected impact
No customer impact is expected, but it cannot be ruled out entirely. Idle (inactive) connections/sessions may time out; active ones should not, as they are synchronized during the startup of a new software release. If you notice anything unusual, such as timeouts of active sessions or the inability to connect to your server, please contact our support.

Affected customers
All IP prefixes routed through our DDoS protection (which is the default).

Fallback plan
Should the update fail and cause issues, we will disconnect the respective filters within a few seconds.

Oct 8, 21:01 CEST

Oct 8, 2026

Completed - The scheduled maintenance has been completed.
Oct 8, 01:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 7, 22:00 CEST
Scheduled - Start: 07.10.2026, 22:00 CEST
End: 08.10.2026, 01:00 CEST

We need to carry out maintenance on the host system vnode14 which is containing PHP-Friends HDD VMs. The VMs will be migrated to other (identical) host systems which involves a short downtime (depending on the disk size of the VM, about 5 minutes per 30 GB). Customers may check in our control panel (SolusVM) if they have any VMs running on vnode14.

To minimize the impact for affected customers, we migrate one VM after another and we will do it over night only (22:00 CEST - 01:00 CEST).

Please make always sure that your VM is configured to be "reboot resistant", so that all software you need starts at boot time and is stopped cleanly when the host system sends an ACPI shutdown signal.

Sep 30, 19:18 CEST