Following the upstream maintenance window that concluded earlier yesterday, we identified an additional incident caused by human error on the datacenter engineers side, which resulted in extended degraded performance on one affected node.

During the power-related works, the engineers were reseating and replacing PSU units on the physical hosts. After replacing one of the power supply units, the server was powered on - however, the second PSU was reconnected only after the system had already fully booted into the OS. As a result of this incorrect power-on sequence, the motherboard triggered an automatic TDP cap, significantly limiting CPU power delivery. This caused severe CPU throttling and led to notable performance degradation on the affected node.

This issue has now been fully resolved. The node has been rebooted under correct power conditions, the TDP limitation has been cleared, and full CPU performance has been restored. All services on the affected node are confirmed to be operating normally.

Only one node (🇩🇪 FC [9555P] vulpes) was impacted by this incident. All other nodes remained fully operational and unaffected throughout.

As compensation for this additional disruption, all customers hosted on the affected node will receive three extra days of service, on top of the other three days already credited for the earlier upstream maintenance.

We sincerely apologize for the inconvenience. This incident was caused by an engineering oversight during the post-maintenance restoration process, and we are reviewing our procedures to prevent recurrence, as well as add more monitoring for cases like this.

Thank you for your patience and understanding.

All nodes are now back online. Please allow up to 20 minutes for VMs to fully start. As compensation for the inconvenience, we're extending our original offer to three days instead of two - all affected customers will receive their compensation within today.

Thank you for your patience through this incident.

VM Node 🇩🇪 FC [9950X] lagopus is back online since 1:39 PM UTC.

The remaining node is 🇩🇪 FC [9555P] vulpes, as well as our internal node that hosts our DNS Panel and ns1.senkodns.net.

VM Nodes 🇩🇪 FC [9950X] pallida, 🇳🇱 [9950X] fulva and 🇩🇪 FC [9950X] ferrilata are back online since 1:20 PM UTC

Unfortunately, maintenance is still being carried out. We apologize for the delay we are currently experiencing with our upstream provider.

🇳🇱 ams-9575f-macrotis node is back online as of 11:36 AM UTC. Work is ongoing to restore full operation across the remaining nodes.

We have just been informed by our upstream provider of planned maintenance currently underway, which is affecting a portion of our virtual server infrastructure.
As a result of this maintenance, 7 out of 69 virtual server nodes, both in Netherlands and Germany locations are currently experiencing downtime. All other nodes remain fully operational and unaffected.

Estimated downtime: 30 – 45 minutes

ℹ️ 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 short notice and the inconvenience caused.

The maintenance is being carried out on the upstream provider's end, and our team is actively monitoring the situation to ensure services are restored as quickly as possible. Affected customers will see their nodes return to full operation automatically once the maintenance window concludes.
We appreciate your patience and understanding, and we will provide a follow-up update once all nodes are confirmed back online.

The maintenance has been completed successfully. The core router of our upstream provider is back online as of 00:12 AM UTC and traffic has shifted back to Helsinki. All services should be operating normally.
Thank you for your patience.

Our network has been stable since 03:51 PM UTC. The attack is continuing at a reduced intensity and is being actively reflected, with blackholing applied where necessary.

During mitigation, our upstream provider discovered a software bug in Arista EOS on their core router - a SIGSEGV crash in the flow sampling daemon that caused the flow collector to become unstable. This most likely allowed a portion of attack traffic to slip through to the upstream network, which contributed to the network downtime our customers have experienced. An emergency upgrade has been scheduled to address this.

Please be aware of the following upcoming maintenance: 7th March 2026 - 00:00 to 00:30 UTC

Our upstream provider will perform an Arista EOS upgrade on their core router in Helsinki. The maintenance is expected to take up to 30 minutes, though completion may come sooner.
Our Finland network will be unavailable for the duration of this window.

In parallel, traffic will be once again routed through our Germany filtering PoP to reflect the ongoing attack. As a result, latency to services hosted in Finland will be elevated both before and after the maintenance window - this is expected and will normalize once the attack subsides and direct routing is restored.
We apologize for the continued disruption and appreciate your understanding. Further updates will follow.

We are observing a recurrence of yesterday's DDoS attack targeting our Finland location. The attack follows the same pattern as before but at a lower volume. Our upstream provider has been notified and is already actively working to mitigate the attack.

We will continue to monitor the situation and provide updates as the mitigation progresses. Thank you for your patience.

Traffic has been successfully rerouted back to our Helsinki location and all services have returned to normal. The attack ceased approximately one hour ago and no further malicious traffic is being observed.

We want to thank our customers for their patience throughout this incident. As a follow-up, we will be implementing automated mitigation solutions to enable faster blackholing and traffic filtering in the future - minimizing the impact of any similar events on your services.

If you experience any lingering issues, please don't hesitate to reach out to our support team.

As part of our ongoing mitigation efforts, we have rerouted all traffic from our Finland location through a scrubbing PoP in Frankfurt, Germany. Active filtering is now in place and network connectivity is being restored.

The attack has since escalated to 8.4 Tbit/s and is carpet-bombing our entire /24 subnet. Despite the scale, our team and upstream provider are successfully filtering the malicious traffic.

As a result of the temporary reroute, you may notice higher latency than usual when accessing Finland-hosted services - this is expected behavior while traffic is being routed through Germany for scrubbing. Normal routing will be reinstated once the attack has subsided.

We continue to monitor the situation in real time and will post further updates as conditions change. Thank you for your patience.

Since 03:44 PM UTC, we have been experiencing a large-scale DDoS attack targeting customers in our Finland location. The attack is causing significant packet loss, increased latency and intermittent inaccessibility of customer services.

The attack volume has exceeded 7 Tbit/s and originates from a globally distributed botnet. Our network engineering team is actively working with upstream providers to mitigate the attack. Traffic filtering and rerouting measures are currently being applied.

We will continue to post updates as the situation develops. Thank you for your patience.