NovaCloud-Hosting Status - Incident history

IP-Tunnel traffic rerouting

Wed, 9 Sep 2026 08:00:00 +0000

Type: Maintenance

Duration: 2 hours

Affected Components: , , , , , ,

Sep 8, 07:08:02 GMT+0
Identified - We will reroute all IP-Tunnel Traffic via our location in Frankfurt am Main in order to reduce the latency for our customers. The maintenance is estimated to take around 30 minutes, where you may experience brief connectivity disruptions. Affected services: High-End DE VPS (NL is excluded from maintenance) IP-Tunnel services.

Sep 9, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Sep 9, 10:00:00 GMT+0
Completed - Maintenance has completed successfully.

VHOST-EPYC01 Mainboard replacement

Mon, 7 Sep 2026 09:50:00 +0000

Type: Maintenance

Duration: 6 hours

Affected Components:

Sep 7, 09:50:00 GMT+0
Identified - Maintenance is now in progress.

Sep 7, 12:32:00 GMT+0
Identified - Due to a problem with the OS, which prevents the hostsystem from starting normally. Our team is currently working on completing the maintenance..

Sep 7, 15:50:00 GMT+0
Completed - Maintenance has completed successfully.

Sep 7, 09:50:33 GMT+0
Identified - Due to the repeated outages caused by hardware problems, we will replace the mainboard of the affected server. Unfortunately, we need to carry out this maintenance on short notice, since we want to prevent further outages in the future. ETA: 1-2 hours.

EPYC-01-VHOST outage

Tue, 25 Aug 2026 21:21:15 +0000

Type: Incident

Duration: 3 hours

Affected Components:

Aug 25, 21:21:15 GMT+0
Identified - EPYC01 is experiencing a hardware failure affecting its NVMe storage. Both NVMe drives reported read and write I/O errors, which degraded the RAID1 array and forced the virtual machine datastore into read-only mode. This has affected running virtual machines and prevented some stopped machines from starting. Our infrastructure provider will replace the complete server barebone on the morning of 26 August 2026\. This includes the hardware responsible for the PCIe and NVMe connections. They will notify us before starting the work. After the replacement, we will verify the RAID and filesystem before starting all affected virtual machines. We expect the issue to be resolved during the morning once these checks are complete. We apologize for the disruption..

Aug 26, 00:21:00 GMT+0
Resolved - This incident has been resolved. If you are still experiencing issues, please contact our support..

EPYC01-VHOST Maintenance

Tue, 25 Aug 2026 09:51:00 +0000

Type: Incident

Duration: 4 hours and 14 minutes

Affected Components:

Aug 25, 14:04:46 GMT+0
Resolved - A defective NVMe SSD has caused IO errors on write operations. We have installed a replacement NVMe and are resyncing the RAID, which may result in lower performance for the next 8 hours. Since there were no clear signs of a faulty NVMe SSD, we assumed an issue with the PCIE Slot or Mainboard, which was not the case. We apologize for the inconvenience caused by this incident..

Aug 25, 09:51:00 GMT+0
Investigating - We had to conduct a small maintenance, since there seems to be an issue with the Raid on the hostsystem. .

Aug 25, 11:10:00 GMT+0
Monitoring - We have rebooted the hostsystem and are currently verifying whether the issue is resolved. All VPS are started up..

Aug 25, 12:24:57 GMT+0
Investigating - Premium VPS are experiencing IO write errors due to what seems to be a defective PCIE slot. Our team is currently investigating the issue..

Aug 25, 12:52:03 GMT+0
Identified - A technician is currently investigating the hardware-issue on-site..

Aug 25, 13:41:55 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Network maintenance FFM2

Mon, 24 Aug 2026 09:30:00 +0000

Type: Maintenance

Duration: 12 hours

Affected Components: ,

Aug 24, 09:30:01 GMT+0
Identified - Traffic is currently being rerouted. There was no interruption, as expected..

Aug 24, 09:17:12 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

Aug 24, 21:30:00 GMT+0
Completed - Maintenance has completed successfully.

EPYC-01-VHOST outage

Mon, 24 Aug 2026 07:05:00 +0000

Type: Incident

Duration: 55 minutes

Affected Components:

Aug 24, 07:05:00 GMT+0
Investigating - We are currently investigating this incident..

Aug 24, 07:10:00 GMT+0
Identified - We have found yet another defective RAM module. We are conducting an emergency maintenace in order to physically try swapping the affected memory modules. If that doesn't resolve the issue, we may have to consider replacing the CPU or Mainboard. .

Aug 24, 07:54:28 GMT+0
Monitoring - We have replaced multiple memory modules and affected VPS are starting up..

Aug 24, 08:00:00 GMT+0
Resolved - This incident has been resolved..

Emergency Maintenance to update hostsystems

Thu, 6 Aug 2026 22:00:00 +0000

Type: Maintenance

Duration: 3 hours and 52 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Aug 6, 20:50:06 GMT+0
Identified - **Scheduled time:** 07 August 2026, 00:00 AM (GMT+2) To address **a critical CVE**, we have scheduled emergency maintenance on all hypervisor and game server nodes at short notice. This maintenance is necessary to apply the required security mitigation and reboot the affected systems. **Expected impact:** Affected services may experience a short downtime due to host reboots. The following services may be affected: * Standard VPS * Premium VPS * High-End VPS * Storage VPS * Storage-Box * Premium Game-Server * Webspaces * Discord Bot instances The estimated outage per affected VPS is approximately **10–30 minutes** within the maintenance window. No action is required on your side. We understand that short-notice maintenance can be inconvenient and sincerely appreciate your understanding as we carry out this work to ensure the continued security and stability of our infrastructure..

Aug 6, 22:00:01 GMT+0
Identified - Maintenance is now in progress.

Aug 7, 01:33:32 GMT+0
Identified - Storage VPS on XEON03-VHOST are currently still unreachable, we are currently implementing a fix. Thanks for your patience..

Aug 7, 01:51:32 GMT+0
Identified - We have resolved the issue on XEON03-VHOST, which prevented us from starting up some VPS. If your VPS is still not running within the next 30 minutes, please contact us via a ticket at support@novacloud-hosting.com.

Aug 7, 01:51:36 GMT+0
Completed - Maintenance has completed successfully..

FFM2 outage

Mon, 20 Jul 2026 08:05:24 +0000

Type: Incident

Duration: 19 days, 5 hours and 55 minutes

Affected Components: , , , , , ,

Jul 20, 17:48:00 GMT+0
Monitoring - All IP-Transit and High-End VPS DE services are currently fully reachable. We are in contact to our infrastructure provider at the FFM2 location to find a solution for our Dedicated Server and Standard VPS DE customers. If you have a Standard VPS DE, you can contact our team at support@novacloud-hosting.com.

Aug 8, 14:00:00 GMT+0
Resolved - This incident has been resolved..

Jul 20, 10:28:00 GMT+0
Identified - IP-Transit and High-End VPS DE are now online. Regarding Dedicated Servers and Standard VPS DE, we are currently waiting for a resolution from our infrastructure provider at the NTT-FRA1 datacenter. Some customers are still reporting issues with TCP connections or Tunnels not working. .

Jul 20, 13:05:30 GMT+0
Monitoring - All GRE, GRETAP and VXLAN Tunnels are now reachable again. Our team is still working on restoring Wireguard Tunnel connectivity. The issue was caused by false filtering of PletX, which dropped TCP connections..

Jul 20, 15:43:48 GMT+0
Monitoring - PletX seems to be blocking GRE packets from multiple source IPs. If you experience any issues with your IP-Transit services, please send us a ticket to support@novacloud-hosting.com, so we can gather more information. We are currently waiting for a solution from our Upstream's NOC. High-End VPS DE are also partially affected..

Jul 20, 08:05:24 GMT+0
Investigating - We are currently investigating this incident..

Jul 20, 09:17:32 GMT+0
Identified - Since we currently don't have an ETA for until FFM2 is normally available again, we are currently working on restoring the IP-Transit services at another location..

EPYC-01-VHOST hardware issue

Sun, 19 Jul 2026 11:54:00 +0000

Type: Incident

Duration: 21 minutes

Affected Components:

Jul 19, 11:54:00 GMT+0
Identified - We are currently experiencing an outage with the EPYC-01-VHOST, affecting all Premium VPS..

Jul 19, 12:00:00 GMT+0
Identified - We have identified a defective RAM module in the affected host system. This caused the system to crash, as the number of memory errors exceeded what ECC could reliably correct. We are currently restarting the host system to bring all affected VPS back online. During the boot process, the system will automatically disable the faulty memory module to prevent further instability while a permanent hardware replacement is arranged. We apologize for the inconvenience and will provide further updates as necessary..

Jul 19, 12:15:00 GMT+0
Resolved - This incident has been resolved. We will conduct a maintenance to replace the defective RAM module..

Emergency Maintenance for CVE-2026-53359

Wed, 8 Jul 2026 05:00:00 +0000

Type: Maintenance

Duration: 1 day

Affected Components: , , , , , ,

Jul 8, 02:06:53 GMT+0
Identified - **Scheduled time:** 08 July 2026, 05:00 AM (GMT+2) To address **CVE-2026-53359**, we have scheduled emergency maintenance on selected hypervisor and game server nodes in both of our locations at short notice. This maintenance is necessary to apply the required security mitigation and reboot the affected systems. **Expected impact:** Affected services may experience a short downtime due to host reboots. The following services may be affected: * Standard VPS * Premium VPS * Storage VPS * Storage-Box * Premium Game-Server * Webspaces * Discord Bot instances The estimated outage per affected VPS is approximately **10–30 minutes** within the maintenance window. ### All other services remain **unaffected** No action is required on your side. We understand that short-notice maintenance can be inconvenient and sincerely appreciate your understanding as we carry out this work to ensure the continued security and stability of our infrastructure..

Jul 8, 05:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 9, 05:00:00 GMT+0
Completed - Maintenance has completed successfully.

XEON03-VHOST-EYG1 hardware problem

Mon, 6 Jul 2026 17:20:00 +0000

Type: Incident

Duration: 2 hours and 45 minutes

Affected Components:

Jul 6, 17:20:00 GMT+0
Investigating - We are currently investigating this incident..

Jul 6, 17:25:00 GMT+0
Identified - Due to an issue with the hardware raid controller, a reboot was necessary to restore normal operation of the HDD Storage. Since all VPS were already actively being affected by this issue, our team has decided to continue with an unannounced reboot to restore normal operation. .

Jul 6, 19:42:38 GMT+0
Monitoring - We implemented a fix and affected VPS are currently being started..

Jul 6, 20:05:00 GMT+0
Resolved - This incident has been resolved..

XEON03-VHOST-EYG1 outage

Sun, 28 Jun 2026 19:45:00 +0000

Type: Incident

Duration: 12 hours and 17 minutes

Affected Components:

Jun 28, 21:32:44 GMT+0
Identified - The technician has completed further diagnostics and replaced all RAM modules, CPU1, and the cooling fans. Unfortunately, none of these measures resolved the issue. Based on the diagnostics, the root cause has been identified as a defective motherboard. Replacing the motherboard is a more time-consuming procedure and requires more time. As a result, the replacement will be carried out by the regular datacenter shift on Monday morning. We will provide another update as soon as the replacement has been completed or new information becomes available..

Jun 29, 07:35:17 GMT+0
Monitoring - The defective motherboard has been successfully replaced by aa technician, and the server is now back online. All VPS are currently starting up and services are being restored. Based on our checks, there has been no data loss as a result of this incident. We will continue to monitor the system closely over the next few hours to ensure everything remains stable. We sincerely apologize for the inconvenience caused and thank you for your patience throughout this incident..

Jun 29, 08:01:51 GMT+0
Resolved - All affected virtual servers have now been successfully started and are operating normally. The incident has been resolved. If you continue to experience any issues with your service, please contact us immediately by emailing [**support@novacloud-hosting.com**](mailto:support@novacloud-hosting.com) or by opening a support ticket through the customer dashboard. As compensation for the downtime, all affected customers will receive **3 days of additional service time**. This compensation will be applied automatically within the next **48 hours**, and we will send an email notification to all affected customers once it has been processed. We sincerely apologize for the inconvenience caused by this unexpected hardware failure and would like to thank you for your patience and understanding throughout the incident..

Jun 28, 19:53:00 GMT+0
Identified - It seems that the server orderly shutdown for a currently unknown reason. There is no hardware fault and the server is currently starting..

Jun 28, 19:45:00 GMT+0
Investigating - We are currently investigating this incident..

Jun 28, 20:17:17 GMT+0
Identified - We have identified a hardware issue affecting the XEON03-VHOST-EYG1 hostsystem. Initial diagnostics indicate a possible failure of either the motherboard or CPU, as CPU1 is unable to detect any installed memory modules. Additionally, the server performed an automatic shutdown after multiple cooling fans failed within a 15-minute timeframe. We have already contacted the datacenter and are currently awaiting their response. Based on the current situation, we unfortunately do not expect the issue to be resolved before Monday morning. We sincerely apologize for the inconvenience caused by this unexpected hardware failure. While incidents of this nature cannot be predicted or prevented, we understand the impact they have on your services and are working with the highest priority to restore the service as quickly as possible. As compensation for the downtime, all affected customers will receive an extension of their service once the incident has been fully resolved. Please note that, due to the ongoing incident, support tickets related to it will be processed on a limited basis until normal operations have been restored. We will continue to provide updates here as new information becomes available..

Jun 28, 20:41:13 GMT+0
Identified - A technician is currently on the way to the datacenter to perform further diagnostics and, if possible, replace the defective hardware on-site. We will provide another update as soon as we have more information..

EPYC-01-VHOST Memory Replacement

Mon, 15 Jun 2026 07:00:00 +0000

Type: Maintenance

Duration: 3 hours and 17 minutes

Affected Components:

Jun 12, 16:23:28 GMT+0
Identified - We have to postpone the planned maintenance to 15.06.2026 between 9:00-13 UTC. Thanks for your understanding..

Jun 15, 07:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 15, 08:56:52 GMT+0
Identified - We are now starting with the replacement of the defective hardware and will shutdown all VMs on the hostsystem..

Jun 15, 09:34:30 GMT+0
Identified - The maintenance is now complete and all VPS are gradually starting up. We expect all VPS to be available in around 5-15 minutes and will provide an update..

Jun 15, 10:17:20 GMT+0
Completed - All VPS are online since 11:43 UTC. If you still experience issues, please immediately create a ticket or send an email to support@novacloud-hosting.com. We apologize for any inconvenience caused by this maintenance and thank for your continued trust in our services..

Jun 11, 22:46:49 GMT+0
Identified - **Emergency Maintenance** We will perform an emergency maintenance on **EPYC-01-VHOST** to replace multiple defective memory modules. During the previous incident, one faulty memory module was successfully disabled during the reboot process. However, we have since identified an additional defective module that was not automatically disabled and is continuing to generate memory errors. While the system is currently operational, it cannot be considered fully stable in its current state. To prevent an unexpected outage and ensure long-term stability, we have decided to replace the affected hardware as soon as possible. **Schedule** We are currently planning to perform the maintenance on **13 June 2026 between 9:00 and 12:00 CEST**. **Expected Impact** * Temporary service interruption of **all Premium VPS** (AMD EPYC VPS) during the maintenance window * Expected maintenance duration: **up to 30 minutes** * Services will automatically resume once the replacement has been completed We apologize for the short notice and any inconvenience this emergency maintenance may cause..

FFM2 Network Improvements

Sat, 13 Jun 2026 12:00:00 +0000

Type: Maintenance

Duration: 27 days, 2 hours and 14 minutes

Affected Components: , , , , , ,

Jun 12, 03:59:48 GMT+0
Identified - **Scheduled:** 13 June 2026, 14:00–17:00 CEST To address the increased latency and packet loss that some customers have experienced during periods of high network utilization since the migration from FFM1 to FFM2, we will be performing network maintenance during the above window. As part of this maintenance, we will: * Increase the router's available bandwidth capacity * Replace the temporary router currently in service with a permanent production router ### Expected Impact A brief service interruption may occur for affected services while traffic is migrated to the upgraded infrastructure. Under normal circumstances, we expect the interruption to last **less than one minute**. However, should any unexpected issues arise during the maintenance, the outage may be extended while corrective actions are performed. ### Why This Maintenance Is Being Performed We have decided to schedule this maintenance on short notice to resolve the latency and packet loss issues as quickly as possible and improve the overall stability and performance of our FFM2 network infrastructure. We apologize for any inconvenience this maintenance may cause and appreciate your understanding..

Jun 13, 12:00:01 GMT+0
Identified - Maintenance is now in progress.

Jun 13, 14:26:02 GMT+0
Completed - Maintenance has completed successfully. We had some issues with IPv6 after migration, which has been fixed after around 10 minutes downtime. IPv4 downtime was minimal, under 2 minutes..

Jun 13, 14:26:44 GMT+0
Completed - i was meaning IPv4 downtime was minimal with under 2 minutes :D.

EPYC-VHOST-01 outage

Thu, 11 Jun 2026 20:04:00 +0000

Type: Incident

Duration: 23 minutes

Affected Components:

Jun 11, 20:04:00 GMT+0
Investigating - It seems that EPYC-VHOST-01 is unresponsible We are currently investigating this incident. .

Jun 11, 20:08:00 GMT+0
Identified - We have identified a defective RAM module in the affected host system. This caused the system to crash, as the number of memory errors exceeded what ECC could reliably correct. We are currently restarting the host system to bring all affected VPS back online. During the boot process, the system will automatically disable the faulty memory module to prevent further instability while a permanent hardware replacement is arranged. We apologize for the inconvenience and will provide further updates as necessary..

Jun 11, 20:17:37 GMT+0
Monitoring - All affected VPS are currently starting up. We expect all services to be fully operational again within approximately 15 minutes..

Jun 11, 20:27:27 GMT+0
Resolved - All affected VPS are now back online and operating normally. If you continue to experience any issues, please open a support ticket or contact us via email at [support@novacloud-hosting.com](mailto:support@novacloud-hosting.com)..

EYG1: Fiber connection to Frankfurt down

Wed, 10 Jun 2026 10:09:00 +0000

Type: Incident

Duration: 1 day

Affected Components: , , , , , , , , , , , , , , , , , , , ,

Jun 10, 10:09:00 GMT+0
Identified - Today at 12:09 CEST, the DCI interconnection towards Frankfurt unexpectedly went down. Traffic was automatically rerouted within a few seconds, but customers with services located in EYG1 may have experienced brief interruptions for connections that were routed via Frankfurt. At the moment, affected EYG1 services may notice increased latency due to the rerouting, but no packetloss or connection issues. Services in all other locations remain unaffected. We are currently waiting for further updates from the upstream/provider and will provide another update once more information is available..

Jun 11, 10:09:00 GMT+0
Resolved - This incident has been resolved..

XEON01-EYG1-VHOST outage

Sat, 6 Jun 2026 20:02:00 +0000

Type: Incident

Duration: 58 minutes

Affected Components:

Jun 6, 20:26:44 GMT+0
Identified - We have identified an issue affecting the host system that caused the underlying filesystem to switch into read-only mode. As a result, some virtual machines may appear locked, become inaccessible, or be unable to start, stop, or access the VNC console. Our investigation has confirmed that this issue is not related to a hardware failure. Instead, it appears to be caused by a software bug introduced by a recent kernel update. To restore normal service, we will reboot the affected host system and revert the problematic update. We are currently working on the resolution and will provide further updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue..

Jun 6, 20:02:00 GMT+0
Investigating - We are currently investigating this incident..

Jun 6, 20:59:51 GMT+0
Resolved - The affected host system has been successfully recovered and all virtual machines are now online again. The underlying issue was caused by a software bug related to a recent kernel update, which resulted in the filesystem being remounted in read-only mode. The affected host has been rebooted and normal operation has been restored. If you continue to experience any issues with your service, please open a support ticket or contact us at [support@novacloud-hosting.com](mailto:support@novacloud-hosting.com) and our team will be happy to assist you. We apologize for the inconvenience and thank you for your patience and understanding..

EYG1 Partial Power maintenance

Fri, 29 May 2026 05:30:00 +0000

Type: Maintenance

Duration: 45 minutes

Affected Components:

May 29, 05:30:00 GMT+0
Identified - On **Friday, 29 May 2026, starting at 07:30 AM (CEST)**, the datacenter will perform maintenance work on the power infrastructure to further improve resilience and ensure uninterrupted power availability in the event of a utility power outage. Most systems are connected to redundant power feeds and will not be affected. However, a limited number of servers require a restart during this maintenance because they are equipped with a single power supply and therefore cannot be connected to both power feeds simultaneously. The maintenance window is scheduled for a maximum duration of **45 minutes**. A few minutes before the maintenance begins, we will perform a graceful shutdown of the affected servers and start them again once the work has been completed. The following dedicated servers are affected: * s200 * s211 * s249 * s541 * s628 We apologize for any inconvenience this may cause and appreciate your understanding..

May 29, 06:15:00 GMT+0
Completed - Maintenance has completed successfully.

EYG1 Partial Power maintenance

Thu, 28 May 2026 05:30:00 +0000

Type: Maintenance

Duration: 45 minutes

Affected Components: , , ,

May 28, 05:30:00 GMT+0
Identified - On **Thursday, 28 May 2026, starting at 07:30 AM (CEST)**, the datacenter will perform maintenance work on the power infrastructure to further improve resilience and ensure uninterrupted power availability in the event of a utility power outage. Most systems are connected to redundant power feeds and will not be affected. However, a limited number of servers require a restart during this maintenance because they are equipped with a single power supply and therefore cannot be connected to both power feeds simultaneously. The maintenance window is scheduled for a maximum duration of **45 minutes**. A few minutes before the maintenance begins, we will perform a graceful shutdown of the affected servers and start them again once the work has been completed. The following dedicated servers are affected: * s544 * s553 In addition, the following virtualization hosts are affected: * RYZEN-01-VHOST-EYG1 * RYZEN-03-VHOST-EYG1 * RYZEN-05-VHOST-EYG1 Virtual machines hosted on these nodes will be unavailable for the duration of the maintenance window and will automatically start again once the host systems are back online. We apologize for any inconvenience this may cause and appreciate your understanding..

May 28, 05:30:01 GMT+0
Identified - Maintenance is now in progress.

May 28, 06:15:00 GMT+0
Completed - Maintenance has completed successfully.

FFM2 network outage

Sun, 24 May 2026 17:13:00 +0000

Type: Incident

Duration: 44 minutes

Affected Components: , , , , , , , ,

May 24, 17:52:03 GMT+0
Monitoring - We are seeing the network recovering. BGP Sessions are up again and network traffic is returning to normal levels. We have not received an official confirmation from our upstream yet..

May 24, 17:57:00 GMT+0
Resolved - A hardware defect on our upstream provider's core router caused a temporary outage at our FFM2 location. Due to a hard failure, a graceful switchover to the standby routing engine was not possible. A full reboot of the system was required, taking approximately 10 to 15 minutes. Following the startup, all BGP sessions successfully recovered. The location is now fully stable, and traffic has returned to normal. We sincerely apologize for the disruption..

May 24, 17:13:00 GMT+0
Investigating - We are currently investigating this incident..

May 24, 17:13:38 GMT+0
Identified - Our Upstream has confirmed an outage of their network equipment of the NTT FRA1 site. A technician has been dispatched..

EYG1 Partial Power maintenance

Fri, 22 May 2026 05:45:00 +0000

Type: Maintenance

Duration: 2 minutes

Affected Components: , ,

May 22, 05:45:00 GMT+0
Identified - On **Friday, 22 May 2026, starting at 07:45 AM (CEST)**, the datacenter will perform maintenance work on the power infrastructure to further improve resilience and ensure uninterrupted power availability in the event of a utility power outage. Most systems are connected to redundant power feeds and will not be affected. However, a limited number of servers require a restart during this maintenance because they are equipped with a single power supply and therefore cannot be connected to both power feeds simultaneously. The maintenance window is scheduled for a maximum duration of **30 minutes**. A few minutes before the maintenance begins, we will perform a graceful shutdown of the affected servers and start them again once the work has been completed. The following dedicated servers are affected: * s544 * s553 In addition, the following virtualization hosts are affected: * RYZEN-07-VHOST-EYG1 * RYZEN-08-VHOST-EYG1 Virtual machines hosted on these nodes will be unavailable for the duration of the maintenance window and will automatically start again once the host systems are back online. We apologize for any inconvenience this may cause and appreciate your understanding..

May 22, 05:45:01 GMT+0
Identified - Maintenance is now in progress.

May 22, 05:46:46 GMT+0
Completed - Maintenance has completed successfully..

Network outage FFM2

Wed, 20 May 2026 22:06:00 +0000

Type: Incident

Duration: 2 hours

Affected Components: , , ,

May 20, 22:06:00 GMT+0
Investigating - We are currently investigating this incident..

May 20, 23:07:47 GMT+0
Identified - Our network has received a DDoS Attack on one of our unprotected subnets. We have taken measures to mitigate the DDoS Attack and are continously working on the issue..

May 20, 23:21:11 GMT+0
Monitoring - The DDoS Attack is now being Mitigated and network reachability is normal again. We are actively monitoring the situation..

May 21, 00:06:18 GMT+0
Resolved - This incident has been resolved..

IP-Router FFM2 outage

Thu, 14 May 2026 23:02:00 +0000

Type: Incident

Duration: 19 minutes

Affected Components: , , , , , , ,

May 14, 23:02:00 GMT+0
Investigating - Our temporary IP-Transit router at the new FFM2 location has shutdown for an unknown reason. We are suspecting a hardware or software issue, nothing related to power or networking. We are currently investigating this incident..

May 14, 23:16:27 GMT+0
Monitoring - We have started the Router and are currently monitoring the situation..

May 14, 23:21:15 GMT+0
Resolved - This incident has been resolved. We are sorry for the inconvenience caused by this incident. This outage would usually have been prevented by our fully redundant IP-Router setup. Unfortunately, due to the current migration from FFM1 to FFM2, we are currently using a single temporary IP-Router while we are moving our normal IP-Routers to the new location. We will evaluate possible solutions to provide full redundancy earlier to prevent further outages. Thanks for your understanding. Impacted services: * Game-Panel * IP-Transit * High-End DE VPS Duration until resolved: 9 Minutes after start of outage.

FFM1 → FFM2 infrastructure migration

Sun, 10 May 2026 08:00:00 +0000

Type: Maintenance

Duration: 10 hours and 45 minutes

Affected Components: ,

May 10, 08:30:00 GMT+0
Identified - Maintenance is now in progress..

May 10, 08:51:12 GMT+0
Identified - After exporting the subnets to the new network, some filtering issues arose, meaning that the endpoints could not be reached properly. We are currently working to resolve these issues; the tunnels remain active on the current infrastructure..

May 10, 10:53:02 GMT+0
Identified - Since we've continued to run into problems, we won't be able to resume for at least two hours. So, for now, things are continuing as usual..

May 10, 08:00:00 GMT+0
Identified - we are writing to inform you about a **planned migration of our infrastructure from FFM1 to FFM2**. The new site is **NTT FRA1** in Frankfurt. **Time window / validity:** 10.05.2026, 10:00–14:00 CEST (UTC+2) We typically expect the downtime itself to take **about 15–30 minutes**. **Unforeseen** issues may extend the window to **up to \~3 hours** in rare cases. If longer impact occurs, it will **not** be one continuous outage for the full duration: we may **temporarily re-announce traffic at FFM1** until stable. The service may **remain intermittently reachable**. We **pre-test** the migration; **edge cases** may still occur that cannot be fully covered in advance. **Impact:** The following services are affected within the scope of this migration: * **IP transit services** * **High-End DE VPS** **All other services** outside this migration are **not affected**. **Background (brief):** We have **planned and built out** the new location over the **past months**. The goal is **more headroom for future expansion** and **additional services**. **Dedicated servers** are already available; **VPS** at this site will follow shortly. **NTT FRA1** is **centrally located in Frankfurt** and offers **comparable certifications** to e.g. Equinix FRA7\. We will continue to expand our **traffic mix** and plan to offer **permanent PletX protection** as a **premium option for demanding workloads**. **IP transit traffic changes (after the migration completes):** * Price per TB (IP transit): **€0.60 → €0.40 (excl. VAT)** * Included traffic per IP from us (IP transit): **500 GB → 1 TB** **Latency:** Globally, latency is **broadly comparable** to before; some destinations see **lower latency** thanks to quality routing in the upstream mix. **Action required:** None, unless you are experiencing any issues after the maintenance has been ended. In this case, immediately create a support ticket so our team can resolve the issue quickly. For questions, please contact our support team as usual..

May 10, 19:15:14 GMT+0
Completed - Maintenance has completed successfully. please open a support-case if you face issues after now..

Migrating PBS01-EYG1 to new machine

Tue, 5 May 2026 21:00:00 +0000

Type: Maintenance

Duration: 4 hours

Affected Components:

May 5, 21:00:00 GMT+0
Identified - PBS01-EYG1 will be migrated onto a new system to increase storage capacity and improve reliability thanks to ECC Memory and redundant Uplinks. You might temporarily not be able to create/restore backups until the migration is done..

May 5, 21:00:01 GMT+0
Identified - Maintenance is now in progress.

May 6, 01:00:00 GMT+0
Completed - Maintenance has completed successfully.

Planned Network Maintenance on 24.04.2026 at EYG1

Thu, 23 Apr 2026 22:00:00 +0000

Type: Maintenance

Duration: 3 hours

Affected Components: , , , , , , , , , , , , , , , , , , , , ,

Apr 23, 22:00:01 GMT+0
Identified - Maintenance is now in progress.

Apr 24, 01:00:00 GMT+0
Completed - Maintenance has completed successfully.

Apr 23, 22:00:00 GMT+0
Identified - **Scheduled Maintenance – EYG1 Upstream Connectivity** Our upstream provider at the EYG1 location has announced short-notice maintenance affecting a transport link to Amsterdam. This maintenance is required to improve long-term network stability. **Time window:** April 24, 2026, 00:00 – 06:00 (UTC+2, CEST) **Expected impact duration:** \~2–3 hours within this window **Expected impact:** During the maintenance, you may experience: * Increased latency * Packet loss * Reduced bandwidth availability To mitigate impact, traffic will be partially rerouted via our Frankfurt PoP. **Background:** A similar maintenance took place on March 20, 2026\. While we understand the inconvenience, these measures are necessary to improve upstream stability. We are currently finalizing a new redundant network PoP in Düsseldorf (Digital Realty), including a dedicated dark fiber connection. Once operational (planned for May 2026), this will eliminate the impact of similar upstream maintenance events in the future. We apologize for any inconvenience caused and appreciate your understanding..

Multiple Servers at EYG1 location unreachable

Thu, 23 Apr 2026 07:33:00 +0000

Type: Incident

Duration: 38 minutes

Affected Components: , , , , , , ,

Apr 23, 07:33:00 GMT+0
Investigating - Multiple of our Hostsystems at the EYG1 location are currently unreachable. We are investigating the issue..

Apr 23, 07:41:00 GMT+0
Monitoring - All affected servers have been started. It seems to be a power-related issue on one of the power feeds, which affected half the servers with non-redundant PSUs. Therefore only AMD Ryzen VPS in Netherlands were partially affected. If your server is still unreachable, please create a support ticket so we can address the issue..

Apr 23, 07:56:39 GMT+0
Identified - RYZEN-07-VHOST-EYG1 is currently still unreachable. A technitian has already been informed about this incident..

Apr 23, 08:11:27 GMT+0
Resolved - RYZEN-07-VHOST-EYG1 is now starting up. All VPS on it should be online within the next 5 minutes..

Apr 23, 08:19:55 GMT+0
Postmortem - On the morning of April 23, a brief utility power failure occurred at the EYG1 data center. One of the Uninterruptible Power Supply (UPS) units failed to engage, causing a total loss of power on one of the power feeds. Servers equipped with only a single Power Supply Unit (PSU) connected to this feed experienced an immediate powerloss. While most systems recovered automatically, the host **RYZEN-07-VHOST-EYG1** suffered a secondary hardware issue that required manual intervention. ### Root Cause Analysis 1. **Power Feed Failure:** An external power dip was not mitigated by a specific UPS system, leading to a localized blackout on one power feed. 2. **Lack of Redundancy:** Impacted Ryzen-based servers utilized non-redundant power configurations. Consequently, the loss of a single feed resulted in an immediate power loss for these machines. 3. **Hardware Damage:** The abrupt shutdown triggered a hardware-level fault on host `RYZEN-07-VHOST-EYG1`, preventing it from rebooting autonomously. ### Incident Timeline * **09:33 AM:** Monitoring alerts triggered for multiple host systems at EYG1\. Investigation initiated. * **09:41 AM:** Issue identified as a power feed failure. Most affected servers were already successfully restarted and entered monitoring status. * **09:56 AM:** All systems recovered except for `RYZEN-07-VHOST-EYG1`. An on-site technician was dispatched to address the hardware failure. * **10:11 AM:** Hardware repair completed. `RYZEN-07-VHOST-EYG1` initiated startup, and all hosted VPS returned to online status shortly thereafter..

EPYC-01-VHOST Memory replacement

Wed, 22 Apr 2026 07:00:00 +0000

Type: Maintenance

Duration: 2 hours and 47 minutes

Affected Components: , ,

Apr 22, 07:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time to replace a defective Memory module. The actual maintenance is not planned to take longer than 30 minutes..

Apr 22, 07:00:01 GMT+0
Identified - Maintenance is now in progress.

Apr 22, 09:44:15 GMT+0
Identified - Defective ram issues is still not resolved we are counting to investigate the issue .

Apr 22, 09:46:37 GMT+0
Completed - Maintenance has completed successfully..

XEON-03-VHOST Memory replacement

Fri, 10 Apr 2026 08:00:00 +0000

Type: Maintenance

Duration: 5 hours and 45 minutes

Affected Components:

Apr 10, 08:00:01 GMT+0
Identified - Maintenance is now in progress.

Apr 10, 13:14:08 GMT+0
Identified - Due to some delays, we had to postpone the maintenance. It will be finished in approximately 30 minutes..

Apr 10, 13:45:00 GMT+0
Completed - Maintenance has completed successfully..

Apr 10, 08:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time to replace a defective Memory module. The actual maintenance is not planned to take longer than 30 minutes..

XEON01-VHOST Outage

Sat, 28 Mar 2026 18:51:00 +0000

Type: Incident

Duration: 1 hour and 40 minutes

Affected Components:

Mar 28, 18:51:00 GMT+0
Investigating - We are currently investigating this incident..

Mar 28, 19:31:24 GMT+0
Identified - We are continuing to work on a fix for this incident. All VMs should be starting within the next 15 minutes..

Mar 28, 20:20:17 GMT+0
Monitoring - All VPS are active again. We are further monitoring the hostsystem to ensure stable operation..

Mar 28, 20:31:21 GMT+0
Resolved - Everything is running stable and as expected. Reverting A system update has fixed a bug, which has caused the issue. We are sorry for the inconvenience caused by this incident and the high resolution time. Thanks for your understanding and continous trust!.

XEON03-VHOST System reset

Tue, 24 Mar 2026 18:30:00 +0000

Type: Incident

Duration: 8 hours and 41 minutes

Affected Components:

Mar 24, 18:30:00 GMT+0
Investigating - We are currently investigating this incident..

Mar 24, 18:45:00 GMT+0
Resolved - XEON03-VHOST seems to have a defective RAM module, which has caused the system reset as the server automatically disabled the affected RAM module. We will replace it in the coming days, which will require a planned maintenance..

XEON03-VHOST Powerloss

Tue, 24 Mar 2026 14:26:00 +0000

Type: Incident

Duration: 41 minutes

Affected Components:

Mar 24, 14:26:00 GMT+0
Investigating - We are currently investigating this incident..

Mar 24, 14:30:00 GMT+0
Identified - XEON03-VHOST had temporarily lost power on both power feeds..

Mar 24, 14:51:45 GMT+0
Monitoring - Most VPS have been started, Storage-VPS on this hostsystem will take around 5-10 minutes until they are reachable again. Thanks for your patience..

Mar 24, 15:06:52 GMT+0
Resolved - All VPS, including Storage-VPS should now be back online. If you still experience issues, please immediately create a ticket on our dashboard and report it to our support team, so we can resolve it quickly. We are sorry for any inconvenience caused by this incident..

PBS01-EYG1

Thu, 19 Mar 2026 14:00:00 +0000

Type: Maintenance

Duration: 8 hours and 49 minutes

Affected Components:

Mar 19, 14:00:00 GMT+0
Identified - PBS01-EYG will undergo a planned hardware upgrade to increase its storage capacity and allow for future scalability. **Maintenance window:** The system will be unavailable for approximately **1–2 hours** during this process. **Post-maintenance:** After the upgrade, a **ZFS pool rebalance** will be performed. During this phase, users may experience **reduced performance** until the process is fully completed. A more precise ETA for the rebalance will be provided once available. We appreciate your understanding..

Mar 19, 14:00:01 GMT+0
Identified - Maintenance is now in progress.

Mar 19, 17:00:00 GMT+0
Completed - Maintenance has completed successfully.

Mar 19, 17:38:26 GMT+0
Identified - Unfortunately the maintenance is not yet completed due to some difficulties with rebuilding the server..

Mar 19, 22:49:06 GMT+0
Completed - Due to some issues with the new Server not booting into the OS, our technician had to revert the upgrade and install the drives back to the old server. We will announce another maintenance for the start of april, where we will migrate to a new Storage system with twice the amount of HDD capacity and redundant 2x10G Uplinks. Thanks for your understanding..

XEON01-VHOST-EYG1 outage

Mon, 9 Feb 2026 17:06:23 +0000

Type: Incident

Duration: 31 minutes

Affected Components:

Feb 9, 17:06:23 GMT+0
Investigating - We are currently investigating this incident..

Feb 9, 17:17:37 GMT+0
Identified - We have found the underlying issue and have fixed the core problem. All VPS should be starting up in 5-10 minutes..

Feb 9, 17:29:09 GMT+0
Monitoring - All VPS have been started. In case your VPS is not working within the next 5 minutes, please create a ticket..

Feb 9, 17:36:58 GMT+0
Resolved - Around **75% of VPS on XEON01-VHOST-EYG1** were affected by this outage. Due to a **software bug**, a backup task for a large VPS was incorrectly written to the **primary NVMe SSD pool** instead of the designated backup storage. The backup file grew to approximately **4 TB**, while the NVMe pool had only around **3 TB** of free capacity available. This caused the storage pool to reach **100% utilization**. Once the primary storage was full, affected virtual machines were no longer able to write to disk. This resulted in widespread I/O errors, and **VM crashes**. As soon as the issue was identified, we immediately removed the incorrectly created backup and began force-restarting all affected VPS instances to restore services as quickly as possible. ### Preventive Measures We have implemented safeguards to ensure this cannot happen again: * Backups can no longer be created on the primary NVMe storage pool under any circumstances. * Additional validation has been added to prevent incorrect backup targets. * We are rolling out improved disk usage monitoring and alerting across all host systems to ensure our team is notified before storage reaches critical levels. We sincerely apologize for this incident. If you are still experiencing any issues caused by this outage, please open a support ticket immediately so we can investigate and resolve it as quickly as possible..

EPYC01-VHOST Packet loss

Thu, 5 Feb 2026 09:00:00 +0000

Type: Incident

Duration: 1 hour and 22 minutes

Affected Components:

Feb 5, 09:00:00 GMT+0
Investigating - EPYC01-VHOST is currently experiencing high packetloss (10-20%) and degraded network performance. We are currently investigating this incident. .

Feb 5, 09:48:00 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Feb 5, 10:22:19 GMT+0
Resolved - This incident has been resolved..

Feb 5, 10:32:53 GMT+0
Postmortem - Due to a DDoS Attack bypassing our Anti-DDoS Filters, the NIC of EPYC01-VHOST was not able to handle the amount of packets, which caused in packetloss and decreased network performance. Unfortunately our monitoring did not immediately report any issues to us. At 10:30 AM GMT+2, our team noticed packetloss on EPYC01-VHOST. At 10:45 AM GMT+2, our team implemented changes to mitigate the issue. We increased ring-buffers on the NIC, increased the max conntrack and contacted our Upstream to mitigate the Attack. After the changes were made, we saw restoration of normal traffic levels and packetloss went back to 0%. We are suspecting that the DDoS Attack was able to bypass the Anti-DDoS Filters, since some of the traffic was originating from an internal DDoS. To prevent this issue from occuring in the future, we will apply these changes to all Hostsystems..

RYZEN02/05-VHOST-DE affected by network outage

Wed, 28 Jan 2026 23:06:00 +0000

Type: Incident

Duration: 49 minutes

Affected Components: ,

Jan 28, 23:06:00 GMT+0
Monitoring - RYZEN02/05-VHOST-DE were affected by a network outage starting at 00:06 GMT+2, which lasted until 00:43 GMT+2\. Everything is online, we are sorry for any inconvenience caused by this incident..

Jan 28, 23:43:00 GMT+0
Monitoring - Traffic levels have returned to normal and we are monitoring the situation..

Jan 28, 23:54:38 GMT+0
Resolved - This incident has been resolved..

Outage RYZEN-08-VHOST

Fri, 14 Nov 2025 13:58:37 +0000

Type: Incident

Duration: 6 hours and 16 minutes

Affected Components:

Nov 14, 20:14:18 GMT+0
Resolved - This incident has been resolved. There have been no further outages except for the 5-minutes when the incident started..

Nov 14, 13:58:37 GMT+0
Investigating - We are currently investigating this incident..

Nov 14, 14:01:12 GMT+0
Identified - All Servers are currently starting up and should be reachable within the next 5 minutes. We are currently further investigating the cause for this incident..

Nov 14, 14:04:09 GMT+0
Monitoring - All servers are back online. If you still experience any problems, please create a ticket so our team can resolve your issue..

Packet loss

Wed, 12 Nov 2025 21:53:14 +0000

Type: Incident

Duration: 2 days and 44 minutes

Affected Components: , , , , , , , , , , , , , , , , , , , , , ,

Nov 12, 21:53:14 GMT+0
Investigating - PletX is receiving a large attack currently causing packet loss on the whole network. Their team is already working on mitigating the effects..

Nov 14, 22:37:00 GMT+0
Resolved - Starting from 21:43 there were massive carpet bombing ddos attacks against our customers/our infrastructure which resulted in - even due to multiple large capacity upgrades during the last weeks and months - sporadic packetloss. Attacks reached around 5 Tbit/s in peak traffic distributed across our network PoPs in NL and DE (Frankfurt). We are aware of this situation and immediately started to work on countermeasures, which were applied after \~22:00. We are further checking options to fully resolve this, but we also need to say that this are attack sizes which we have not seen before like this. These attacks are probably related to the Aisuru botnet which is currently targeting multiple companies and is reaching bandwidths not seen like this before. We are actively monitoring the situation and thank you in advance for your understanding!.

IP-Transit FFM1 - Migration of one Router

Thu, 30 Oct 2025 19:00:00 +0000

Type: Maintenance

Duration: 26 minutes

Affected Components:

Oct 30, 19:00:00 GMT+0
Identified - We will be moving one of the routers to a different data center. At that time, we will make preparations for this and shut down the router as planned. This is for informational purposes only; no outage or packet loss is expected, as we will reroute everything beforehand..

Oct 30, 19:00:01 GMT+0
Identified - Maintenance is now in progress.

Oct 30, 19:26:26 GMT+0
Completed - Maintenance has completed successfully..

IP-Transit FFM1 - Maintenance work for Wireguard Customers

Sun, 26 Oct 2025 11:00:00 +0000

Type: Maintenance

Duration: 6 hours and 15 minutes

Affected Components:

Oct 26, 11:00:00 GMT+0
Identified - If you do not have Wireguard IP transit with us, you can simply take this as information that we are working on the routers at this time; you should not expect any outages or interruptions since traffic is rerouted bevore changes. With this maintenance window, we would like to solve a issue affecting some Wireguard Customers. This is related to the parallel operation of multiple routers and the fact that connections are not maintained properly, there is a small proportion of Wireguard customers who regularly experience instability or disconnections from the Wireguard tunnel. A solution has been developed and will be implemented during this period. There will be minor interruptions for WireGuard during this period..

Oct 26, 11:00:01 GMT+0
Identified - Maintenance is now in progress.

Oct 26, 17:01:44 GMT+0
Identified - The necessary changes have been implemented. You may need to restart the tunnel on your side..

Oct 26, 17:14:44 GMT+0
Completed - Maintenance has completed successfully..

High-End Game Servers – Network & DDoS Protection Upgrade

Sat, 11 Oct 2025 10:00:00 +0000

Type: Maintenance

Duration: 15 minutes

Affected Components: ,

Oct 11, 10:00:00 GMT+0
Identified - We will perform maintenance on all High-End Game Hosting servers to improve network stability and DDoS protection. During this maintenance, IP addresses will change. If you are using a domain to connect to your server, please make sure you are using the domain name instead of the IP address, as the old IPs will no longer be valid. All servers will be automatically restarted. You don’t need to manually shut down your server — the system will gracefully stop all active servers and automatically start those that were online before the maintenance. We appreciate your understanding as we work to enhance performance and reliability..

Oct 11, 10:00:01 GMT+0
Identified - Maintenance is now in progress.

Oct 11, 10:15:00 GMT+0
Completed - Maintenance is now in progress.

AMD Ryzen vHosts network connectivity issues

Sun, 31 Aug 2025 19:00:00 +0000

Type: Incident

Duration: 1 hour and 21 minutes

Affected Components: , , , , , , , ,

Aug 31, 19:00:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

Aug 31, 19:22:00 GMT+0
Resolved - This incident has been resolved..

Sep 1, 23:14:58 GMT+0
Postmortem - # Postmortem: AMD Ryzen vHosts Network Connectivity Issues **Incident Start:** 31 August 2025, 9:00 PM CEST **Incident End:** 31 August 2025, 9:22 PM CEST **Duration:** Approximately 22 minutes **Impact:** Major outage on Ryzen vHosts, particularly RYZEN-05 and RYZEN-08 ## Summary On 31 August 2025, a router misconfiguration caused a significant network outage affecting multiple Ryzen-based vHosts and services. The issue began at 9:00 PM CEST and was fully resolved by 9:22 PM CEST. ## Impact * RYZEN-05 and RYZEN-08 experienced full network loss for about 15 minutes. * All other Ryzen vHosts were briefly disconnected for approximately 10 seconds during the network recovery process. * Affected services included: * DB01 - Game-Cloud Infrastructure * Ryzen Game-Server Nodes (EYG1) * AMD Ryzen/High-End Root servers All customers with services on RYZEN-05 and RYZEN-08 are eligible to receive **2 days of additional runtime credit**. Please open a support ticket to request this credit. ## Root Cause A router misconfiguration combined with an automation error caused connectivity issues on RYZEN-05 and RYZEN-08\. Full restoration required reapplying routing configuration across all nodes, resulting in a brief interruption to all Ryzen vHosts. ## Resolution * A temporary automation fix was deployed to prevent recurrence of this specific issue. * Manual configuration changes restored full network connectivity by 9:22 PM CEST. ## Preventive Actions 1. Implement per-node VM connectivity monitoring for faster detection and resolution. 2. Improve automation workflows to avoid similar misconfigurations. 3. Add validation checks to prevent faulty network configurations from being deployed. We apologize for the disruption and appreciate your patience as we implement additional safeguards to strengthen our network stability..

Multiple RYZEN VHOSTs + Dedicated servers unreachable

Tue, 29 Jul 2025 18:34:46 +0000

Type: Incident

Duration: 46 minutes

Affected Components: , , , , , ,

Jul 29, 19:20:50 GMT+0
Resolved - This incident has been resolved..

Jul 29, 18:34:46 GMT+0
Investigating - We are currently investigating this incident..

Jul 29, 18:41:58 GMT+0
Identified - There was a powerloss on one of the power feeds. It seems that the power has been restored within a few minutes and we are awaiting a statement from the datacenter to what has been affected and why. All affected Dedicated Servers and Root-Servers have already been started..

Jul 29, 19:14:22 GMT+0
Postmortem - ### Summary, Between 20:29 and 20:32 GMT+2, several systems became temporarily unreachable due to a power distribution issue at the datacenter. The incident impacted specific power feeds and affected servers equipped with only a single power supply unit (PSU). ### Affected Systems, * **Virtual Servers:** RYZEN-VHOST 01, 03, 04, 05, * **Dedicated Servers:** A small number of systems with single-PSU configurations, * **Unaffected:** The majority of our infrastructure remained fully operational, including all dual-PSU systems, ### Root Cause, The incident was caused by a fault in one of the datacenter’s internal power subdistribution units. This resulted in a brief power loss on a specific feed. ### Resolution, Power was automatically restored by the datacenter within less than a minute. All affected systems came back online shortly afterward. We have confirmed that no data loss occurred. We are sorry for any inconvenience caused by this incident. Please open a ticket immediately if you still experience an outage, so we can address the issue. .

IP-Transit FFM1 - System replacement and upgrades

Sun, 20 Jul 2025 04:00:00 +0000

Type: Maintenance

Duration: 12 days and 23 hours

Affected Components:

Jul 20, 04:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 20, 04:00:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time. This is our response to repeated minor interruptions since the migration from FRA1 to FFM1\. Specifically, we will: \- Increase the total processing bandwidth from 20 Gbps to 80 Gbps, i.e. quadruple it. \- Replace the currently heavily loaded system with 2 new future-proof systems \- Switchover to a BGP multipath setup for consistent redundancy and maximum reliability For affected customers, this means that there may be several outages during the maintenance-window until the work has been completed. We apologize for any inconvenience caused..

Jul 20, 04:04:00 GMT+0
Identified - since about 06:04 the load is already fully active on the new routers, please open a ticket if you encounter problems, currently everything seems to have worked as planned..

Jul 20, 07:09:51 GMT+0
Identified - even if everything is currently running, the measures are not yet fully completed. we will leave this window open until all work is completed so that parallel operation of the routers works without any problems. at the moment, however, gretap, vxlan, wireguarda and gre should work until we continue later..

Jul 20, 04:23:54 GMT+0
Identified - ok seems like that we have some issue going on after some runtime, looking into it....

Jul 23, 21:59:00 GMT+0
Completed - Maintenance has completed successfully. Since July 23, 2025, the setup has been successfully operating in active-active mode on both routers..

router1.ffm1 is down

Thu, 17 Jul 2025 03:27:00 +0000

Type: Incident

Duration: 3 hours and 20 minutes

Affected Components:

Jul 17, 06:00:00 GMT+0
Identified - We are currently investigating a potential issue with our BGP announcements. Based on external reachability tests, it seems that a significant portion of the internet is unable to reach our endpoint, suggesting that traffic is not being properly propagated or accepted by certain upstream networks..

Jul 17, 03:27:00 GMT+0
Investigating - is down at the moment. This incident was automatically created by Instatus monitoring..

Jul 17, 06:46:33 GMT+0
Resolved - is back up. This incident was automatically resolved by Instatus monitoring..

Jul 17, 06:43:43 GMT+0
Postmortem - ### **Summary** On July 17th, 2025, starting around 05:30 GMT+2, we experienced a partial connectivity issue affecting traffic to the endpoint 5.83.150.1\. A portion of external networks was unable to reach some prefixes including 5.83.150.0/24, while others remained fully functional. Initial observations pointed towards a potential BGP routing problem, but external route propagation appeared fully intact across all monitors. ### **Root Cause** The issue was caused by a malfunctioning SmartMitigate DDoS filtering node within the upstream provider's infrastructure. The affected host had stopped forwarding traffic. As a result, incoming traffic that was routed through this specific mitigation node was effectively dropped, leading to asymmetric reachability depending on which SmartMitigate host was assigned. This incident was not related to our own BGP announcements or configurations. ### **Resolution** The upstream provider identified the faulty SmartMitigate host and removed it from operation. Immediately afterward, traffic flows normalized and full connectivity to the affected prefix was restored. This occurred around 09:20 GMT+2. ### **Impact Overview** * **Affected Prefix:** 5.83.150.0/24 * **Root Cause:** Faulty SmartMitigate (DDoS filter) node * **BGP Status:** Unaffected – all routes remained correctly announced and visible * **Duration:** \~3 hours 50 minutes * **Impact:** Partial traffic loss (limited to traffic routed via the affected SmartMitigate node) ### **Current Status** Connectivity has been fully restored. The root cause has been addressed at the upstream provider level. No further disruptions are expected related to this issue..

Game-Host Maintenance

Thu, 3 Jul 2025 01:00:00 +0000

Type: Maintenance

Duration: 6 minutes

Affected Components: , , , , , ,

Jul 3, 01:00:01 GMT+0
Identified - Maintenance is now in progress.

Jul 3, 01:00:00 GMT+0
Identified - We are planning a maintenance on all of our Game-Host, to change some parameters, to solve a problem with large Minecraft Servers crashing randomly. The maintenance includes a full restart of all servers. It is not necessary to shutdown the servers before the maintenance starts, the system will gracefully shutdown all Servers and start up all servers which were online before the maintenance automatically..

Jul 3, 01:05:32 GMT+0
Completed - Maintenance has completed successfully..

Network Migration: IP-Transit FRA1 -> FFM1

Fri, 30 May 2025 20:45:00 +0000

Type: Maintenance

Duration: 12 days, 13 hours and 25 minutes

Affected Components: , , , , ,

Jun 1, 01:22:24 GMT+0
Completed - Maintenance has completed successfully. Since everything has been running for over 15 hours, the maintenance is considered complete. If you register any problems, please open a ticket..

May 30, 20:45:01 GMT+0
Identified - Maintenance is now in progress.

May 30, 21:46:00 GMT+0
Identified - Most prefixes are back since 23:46..

May 31, 00:30:00 GMT+0
Identified - other Updates: * Announcement of some prefixes did not pass, fixed since 00:18 * IPv6 NDP Issues due to Large Amount of IPs and broken local-link, fixed since \~02:25 * Wireguard fixed.

May 30, 20:45:00 GMT+0
Identified - As all IP-Transit customers have already received an e-mail about, we will completely migrate our IP-Transit FRA1 infrastructure to a new Location FFM1 and new Routers. Details are in that e-mail. Please note that there may be several shorter and longer outages during this period. However, we do not expect any major downtimes. After the planned disannounce of all prefixes at 23:00 we will announce all prefixes at the new location in a timely manner. After that, once a connection has been established for the first time, no further outages are to be expected until the end of the maintenance window. As soon as the announcements at the new location have been started, we will post it here. It can take up to 24 hours for all routers out there to accept the new routes, but in most cases this will be much shorter, like some minutes to 1 hour (depends on your ISP and their Upstreams). All precautions have been taken on the upstream side so that the filters allow the new announcements immediately. If you think that something is not working as it should after the changeover, please do not hesitate to open a ticket..

May 31, 10:16:18 GMT+0
Identified - Our IPv6 Endpoint is also working since 12:16 finally, there was some error with the prefix. we will apply last optimizations to the automation during the day..

Customer Dashboard maintenance - investigating backend issue

Thu, 29 May 2025 20:05:00 +0000

Type: Maintenance

Duration: 1 hour

Affected Components: ,

May 29, 20:05:01 GMT+0
Identified - Maintenance is now in progress.

May 29, 20:05:00 GMT+0
Identified - We are performing an urgent maintenance to investigate an issue with the backend of the system, causing some small issues which need to be fixed. .

May 29, 21:05:00 GMT+0
Completed - Maintenance has completed successfully.

Root-Server High-End (AMD Ryzen) Migration

Wed, 14 May 2025 09:00:00 +0000

Type: Maintenance

Duration: 17 hours and 21 minutes

May 15, 02:21:15 GMT+0
Completed - The maintenance was successfully completed last evening. Some VPS had to be rebooted to apply some changes to the network configuration, but all IP-addresses are still the same. IPv6 was not reachable for a few hours, but the issue was solved after finishing the migration work. We appreciate your continous trust in NovaCloud-Hosting.

May 14, 09:00:01 GMT+0
Identified - Maintenance is now in progress.

May 14, 09:00:00 GMT+0
Identified - All AMD Ryzen Root-Servers currently running on **Ryzen 9 7900** CPUs will be migrated to upgraded systems featuring **Ryzen 9 7950X3D**, **9900X**, or **7900X** CPUs. Systems with the 7900X will be further upgraded to 9900X in the coming weeks. This upgrade will improve overall performance. **Pricing remains unchanged** — there will be no increase for existing servers. ### Migration Details: * **IP-Addresses will stay the same** * The migration will be performed **live**, without planned downtimes. * **Network disruption** of a few seconds up to 5 minutes may occur. * A **server reboot** may be required (completed within a few minutes). The new infrastructure has been thoroughly tested to ensure stability and minimal disruption. If any issues arise after the migration, please open a support ticket..

XEON-01-VHOST Maintenance

Wed, 16 Apr 2025 12:00:00 +0000

Type: Maintenance

Duration: 12 days, 4 hours and 34 minutes

Affected Components: , ,

Apr 28, 22:38:48 GMT+0
Completed - We have successfully changed to a reliable and fast Storage-Layout. You can now enjoy high performance as usual..

Apr 16, 12:00:00 GMT+0
Identified - The issue doesn't seem to be solved permanently and occurs from time to time, causing downtimes. We are planning a maintenance for 17.04.2025, where all VMs will be migrated onto another hostsystem temporarily in order to reconfigure the Storage layout of the Intel Xeon HDD Pool. All affected customers with Storage Servers will be awarded 5 days of runtime and all customers with Intel Xeon servers 2 days of runtime. Please open a ticket after the maintenance has finished in order to receive the compensation. All tickets opened before the maintenance has finished will be put on hold and processed once we have finished the migration. We are extremely sorry for the inconvenience caused by these incidents and hope you can keep your trust in us after we've finished this maintenance, which will solve the problems permanently in order to deliver the quality and reliability we always strive to achieve..

Apr 17, 12:00:00 GMT+0
Identified - We are planning to further investigate the outage from this morning In order to prevent data-loss, all servers will be stopped while this maintenance is conducted..

Apr 16, 18:05:16 GMT+0
Identified - We are going to migrate all servers onto another hostsystem which we've deployed today. Thanks to the new hostsystem being an Intel Xeon with enough ressources, it won't be necessary to stop any servers. Therefore, we don't expect any significant outages caused by the maintenance. There may be a reboot of the servers, which shouldn't last longer than a few minutes..