History
Jul 2026 - Sep 2026
August 2026
Outage
ams-9950x-odessana outage
Affected services:
🇳🇱 [9950X] odessana
Resolved
After a thorough investigation, we identified the root cause of the incident: a software issue between the AMD platform and IOMMU caused the PCI devices backing the NVMe drives on cluster node ams-9950x-odessana to malfunction on a software level, forcing the system to switch into a read-only mode and render the VMs unoperable.

The issue was initially misdiagnosed as a drive failure, which led to an extended delay while we requested remote hands at the data center to replace the suspected faulty drive. Further diagnosis revealed the actual cause. We adjusted the BIOS settings accordingly, then gracefully recovered and resynced the RAID array on the node.

All of the VMs are back up since 00:04 AM UTC, and all customer data is safe. However, we strongly recommend running a file system check on any virtual machines hosted on ams-9950x-odessana to rule out any latent issues.

We sincerely apologize for the disruption and the extended downtime. We will be providing two extra days of service time to all customer services that were affected by this outage.
Sep 01, 12:22 AM
Update
We are continuing our work on resolving the issue.
Aug 31, 9:47 PM
Identified
We found the cause of the issue and are working with the data center engineers to diagnose and resolve it as soon as possible.
Aug 31, 6:56 PM
Investigating
We are investigating the issue on the ams-9950x-odessana node in the Netherlands.
Aug 31, 5:55 PM
Outage
Post-Maintenance Incident
Affected services:
🇳🇱 [9575F] vulpes
🇩🇪 FC [BUDGET] EPYC-3 - VM Status
🇩🇪 FC [9555P] rooki - VM Status
🇩🇪 FC [BUDGET] EPYC-3
🇳🇱 [9575F] odessana - VM Status
🇳🇱 [9575F] odessana
+6 more
Resolved
During planned maintenance affecting five cluster nodes in our fra-9950X cluster, the data center power phase was brought down as scheduled. Due to the interaction between the motherboard firmware and the redundant power supply configuration used on these servers, the motherboards locked CPU frequency to 600 MHz. This caused severe performance degradation and VM outages for customers hosted on the affected nodes.

Affected cluster nodes:
fra-9275f-odessana
fra-9555p-rooki
fra-9375f-budget-2
fra-9334-budget-3

Separately and unrelated to the incident above, our Netherlands location experienced an issue with the VM platform that caused a partial networking malfunction, resulting in outages on:
ams-9575f-vulpes
ams-9575f-odessana
This has already been resolved and no further action is required.

ℹ️ This is an unplanned incident. No action is required from customers at this time. We will automatically provide two extra days of service to all impacted customers as compensation for this incident.

We sincerely apologize for the inconvenience. This incident was not something we could have anticipated. The issue has already been resolved, and our team has restored full performance across all affected nodes.

Thank you for your patience and understanding.
Aug 27, 12:48 PM
Identified
We are investigating the issues with the cluster nodes fra-9275f-odessana, fra-9555p-rooki, fra-9375f-budget-2, fra-9334-budget-3, ams-9575f-vulpes, ams-9575f-odessana
Aug 27, 11:35 AM
Maintenance
Power Maintenance on VPS Nodes in Germany
27 Aug 11:00 - 27 Aug 13:50 2026 UTC
Estimated duration: 2 hours 50 minutes 36 seconds
Affected services:
🇩🇪 FC [9950X] otocyon - VM Status
🇩🇪 FC [9950X] otocyon
🇩🇪 FC [9950X] urocyon
🇩🇪 FC [9950X] urocyon - VM Status
🇩🇪 FC [9950X] chama
🇩🇪 FC [9950X] chama - VM Status
+4 more

Update: The power maintenance at our fra-9950X cluster has been completed ahead of schedule. Power is restored, all affected nodes are back online and VMs are already starting up.


--


On August 27th, 2026, our datacenter in Frankfurt will carry out planned maintenance on part of the facility's power distribution as part of an ongoing modernization of the site's power supply. A number of our German cluster nodes are located in the affected area and will need to be powered down for the duration of the work.


The maintenance is scheduled for August 27th, 2026, from 11:00 AM UTC and is expected to be completed by 4:00 PM UTC.


To prevent any risk of data loss or filesystem damage, we will cleanly shut down all VPS instances on the affected nodes shortly before the power shutdown at 11:00 AM UTC. Power is expected to be restored from approximately 1:00 PM UTC, after which the affected nodes will be brought back online one by one. Customers should therefore expect their VPS to be offline for several hours during this window.


No action is required from clients. All virtual servers will automatically come back online once their host node has been powered up and verified.


This maintenance affects the listed VPS nodes only. All of our other services and locations remain fully operational and are not impacted in any way.


Affected cluster nodes:


fra-9950x-otocyon

fra-9950x-urocyon

fra-9950x-chama

fra-9950x-bengalensis

fra-9950x-rooki


If you experience any issues following the maintenance window, please don't hesitate to reach out to our support team through tickets in the Client Area, Telegram support bot or over e-mail ([email protected]).


Thank you for your understanding.

Aug 18, 8:57 AM
Maintenance
[Scheduled] Infrastructure Relocation of VPS Nodes in Finland
27 Aug 11:00 - 04 Sep 18:15 2026 UTC
Estimated duration: 8 days 7 hours 15 minutes
Affected services:
🇫🇮 HT [9454P] rueppellii - VM Status
🇫🇮 HT [9454P] rueppellii
🇫🇮 HT [9454P] velox
🇫🇮 HT [9454P] velox - VM Status
🇫🇮 HT [9454P] macrotis
🇫🇮 HT [9454P] macrotis - VM Status
+45 more

As of September 4th, 2026, our infrastructure upgrade in Helsinki is officially complete. Every cluster node has been successfully relocated into our rack and is now running on our own network equipment.

This maintenance marks a major milestone for us. With direct control over the network at our Finland location, we now have the foundation to further develop the location and significantly improve network connectivity for all of our customers - with more capacity, better routing and faster rollout of improvements going forward.


All virtual servers are back online and operating normally. If you notice any issues following the relocation, please reach out to our support team through tickets in the Client Area, Telegram support bot or over e-mail ([email protected]).


We'd like to sincerely thank everyone for their patience throughout the maintenance window. We know a window of this length isn't very convenient, and we truly appreciate your understanding - the result will be well worth it.

And just one more thing: keep an eye out - a huge announcement is coming soon for all of our users in Finland.

Thank you for being with us!


--

Starting today, August 27th, 2026, we are beginning a major infrastructure upgrade at our Finland location. All of our servers in Helsinki will be relocated into our rack and connected to our own network equipment.


This move is a necessary step for the further development of the location. It gives us direct control over the network, allowing us to significantly improve connectivity, increase capacity and roll out further improvements to the location going forward.


The maintenance begins on August 27th, 2026 and is estimated to be completed by September 4th, 2026.


The relocation will be carried out node by node. Each cluster node will be cleanly shut down, physically moved into our rack, reconnected to our equipment and configured, after which all virtual servers on that node will become reachable again. Estimated downtime is between 2 and 4 hours per cluster node, though a faster turnaround is possible.


As the physical transfers are performed by datacenter engineers, we are unable to provide strict per-node timetables. Transfers will be carried out during daytime hours and completed before peak hours (8:00 PM UTC) in order to minimize inconvenience for our customers.


No action is required from clients. All virtual servers will automatically come back online once their host node has been relocated, reconnected and verified. We do recommend ensuring that your software is configured to start automatically after a reboot.

This maintenance affects the listed Finland VPS nodes only. All of our other services and locations remain fully operational and are not impacted in any way.


Affected cluster nodes:

  1. hel-9454p-rueppellii (transfer complete)
  2. hel-9454p-velox (transfer complete)
  3. hel-9454p-macrotis (transfer complete)
  4. hel-9454p-vulpes (transfer complete)
  5. hel-9454p-corsac (transfer complete)
  6. hel-9454p-zerda (transfer complete)
  7. hel-9454p-odessana (transfer complete)
  8. hel-9454p-culpaeus (transfer complete)
  9. hel-9454p-bengalensis (transfer complete)
  10. hel-9454p-fulva (transfer complete)
  11. hel-9454p-cana (transfer complete)
  12. hel-9454p-otocyon (transfer complete)
  13. hel-7950x3d-cana (transfer complete)
  14. hel-7950x3d-corsac (transfer complete)
  15. hel-7950x3d-bengalensis (transfer complete)
  16. hel-7950x3d-chama (transfer complete)
  17. hel-7950x3d-urocyon (transfer complete)
  18. hel-7950x3d-odessana (transfer complete)
  19. hel-7950x3d-rueppellii (transfer complete)
  20. hel-7950x3d-macrotis (transfer complete)
  21. hel-7950x3d-velox (transfer complete)
  22. hel-7950x3d-vulpes (transfer complete)
  23. hel-7950x3d-zerda (transfer complete)
  24. hel-7950x3d-fulva (transfer complete)
  25. hel-7950x3d-arctic (transfer complete)
  26. hel-7950x3d-culpaeus (transfer complete)


If you experience any issues following the relocation of your node, please don't hesitate to reach out to our support team through tickets in the Client Area, Telegram support bot or over e-mail ([email protected]).


We understand that a maintenance window of this length may cause inconvenience and we appreciate your patience. This is a mandatory step for us to keep growing and improving our services, and we're confident the result will be well worth it.


Thank you for your understanding.

Aug 26, 8:00 PM
Maintenance
[Urgent] Critical Security Maintenance
06 Aug 20:00 - 06 Aug 20:42 2026 UTC
Estimated duration: 42 minutes
Affected services:
🇩🇪 FC [9950X] zerda
🇩🇪 FC [9950X] zerda - VM Status
🇩🇪 FC [9950X] bengalensis
🇩🇪 FC [9950X] bengalensis - VM Status
🇩🇪 FC [9950X] cana
🇩🇪 FC [9950X] cana - VM Status
+24 more
July 2026
Maintenance
[Urgent] Security Maintenance on VPS Nodes
07 Jul 23:15 - 08 Jul 04:00 2026 UTC
Estimated duration: 4 hours 45 minutes
Affected services:
🇩🇪 FC [9950X] pallida
🇩🇪 FC [9950X] pallida - VM Status
🇩🇪 FC [9950X] rooki
🇩🇪 FC [9950X] rooki - VM Status
🇩🇪 FC [9950X] otocyon
🇩🇪 FC [9950X] otocyon - VM Status
+49 more

We will be carrying out urgent security maintenance across 1/3 of our VPS nodes to address a critical security matter and keep our infrastructure protected.


A reboot of all VPS instances hosted on the impacted nodes will take place during this maintenance. As a result, customers should expect a brief service interruption of up to 15 minutes per VPS while their server reboots. No further impact is expected beyond this short reboot.


🕐 The maintenance is scheduled for July 7th, 2026, from 11:15 PM UTC and is expected to be completed on July 8th, 2026 by 3:00 AM UTC.


No action is required from clients. All virtual servers will automatically come back online once they have been rebooted.


This maintenance affects VPS nodes only. All of our other services remain fully operational and are not impacted in any way.


Impacted cluster nodes:

🇩🇪 Frankfurt (fra01)

  1. fra-9950x-pallida
  2. fra-9950x-rooki
  3. fra-9950x-otocyon
  4. fra-9950x-zerda
  5. fra-9950x-velox
  6. fra-9950x-ruepellii
  7. fra-9950x-vulpes
  8. fra-9950x-urocyon
  9. fra-9950x-corsac
  10. fra-9950x-cana
  11. fra-9950x-ferrilata
  12. fra-9950x-odessana
  13. fra-9950x-lagopus
  14. fra-9950x-bengalensis
  15. fra-9950X-macrotis
  16. fra-9950x-chama
  17. fra-9375f-budget-2
  18. fra-6140-budget-7
  19. fra-3700x-storage-1
  20. fra-9575f-zerda
  21. FRA Game 1


🇳🇱 Amsterdam (ams01)

  1. ams-9950X-velox
  2. ams-9575f-macrotis
  3. ams-9950x-fulva


🇫🇮 Helsinki (hel01)

  1. hel-7950x3d-rueppellii
  2. hel-7950x3d-macrotis
  3. hel-9454p-otocyon


If you experience any issues following the maintenance window, please don't hesitate to reach out to our support team for assistance. You may contact us through tickets in the Client Area, Telegram support bot or over e-mail.


Thank you for your understanding as we work to keep our infrastructure and customer servers secure.


--


04:00 AM UTC


The urgent security maintenance is now fully completed. All cluster nodes have been patched, rebooted, and are operating normally.


Rather than taking everything down at once, we worked through each cluster node one by one - this kept simultaneous downtime across affected nodes to a minimum and let us apply the necessary changes precisely on each host. Because of the nature of the fix, some nodes required structural changes and took longer to process than others, so thanks for bearing with us while that was done carefully across the fleet.


This addressed a recently disclosed Linux kernel vulnerability, Januscape (CVE-2026-53359). In simple terms: it's a flaw in KVM, the technology that keeps each virtual server isolated from the physical host and from other customers on the same machine. Under specific conditions, it could let a malicious VM break out of that isolation and compromise the host, if nested virtualization was enabled on the host. It had gone unnoticed for ~16 years (!) and affects both Intel and AMD systems.


We have no indication it was ever exploited on our infrastructure — this was a proactive patch applied as soon as fixes landed, which required a kernel update and reboot on each node.


No action is required from clients. Everything is back online.

If you run into any issues, reach out to our support team and we'll be glad to help.

Jul 07, 10:15 PM