Update - The A-Feed is now back on municipal grid power and remains UPS-protected, as reported previously. Due to a faulty module that caused today's issue, the UPS cluster for the A-Feed is currently operating with reduced redundancy (N instead of N+1). Repair is scheduled for tomorrow. We will keep you updated.
Apr 21, 2026 - 18:57 CEST
Monitoring - The load on Feed A is back under UPS protection; power is currently being supplied via generator and will be switched back to the utility grid shortly.
Apr 21, 2026 - 14:57 CEST
Identified - During routine maintenance of the UPS array for the A Feed, a malfunction occurred in one of the UPS modules. As a result, the system switched to bypass mode (automatically as intended), and the A Feed is currently running on emergency power. There was no impact on the IT infrastructure at any time.
The datacenter operator is working with the the manufacturer to resolve the issue as quickly as possible and will switch back to normal operation once the issue is resolved.
Till then, power on the A feed is not redundant and depending on emergency power.
We will keep you updated on the progress.

Apr 21, 2026 - 09:00 CEST
[dataforest Backbone] Interxion FRA8 Operational
90 days ago
99.9 % uptime
Today
Edge Network (affects all locations) Operational
90 days ago
100.0 % uptime
Today
DDoS Protection (affects all locations) Operational
90 days ago
99.6 % uptime
Today
Dedicated Servers (40G / 100G / 400G) Operational
90 days ago
100.0 % uptime
Today
Facilites Operational
90 days ago
100.0 % uptime
Today
[Datacenter] maincubes FRA01 Operational
90 days ago
99.99 % uptime
Today
Datacenter Routing and Switching Infrastructure Operational
90 days ago
100.0 % uptime
Today
Ceph Cluster Operational
90 days ago
100.0 % uptime
Today
Virtual Servers Operational
90 days ago
99.99 % uptime
Today
Managed Servers Operational
90 days ago
100.0 % uptime
Today
Dedicated Servers Operational
90 days ago
100.0 % uptime
Today
Plesk Web Hosting Operational
90 days ago
100.0 % uptime
Today
TeamSpeak3 Servers Operational
90 days ago
100.0 % uptime
Today
Network Storage Operational
90 days ago
100.0 % uptime
Today
Colocation Racks Operational
90 days ago
100.0 % uptime
Today
Facilites Operational
90 days ago
100.0 % uptime
Today
[Datacenter] firstcolo FRA4 Operational
90 days ago
99.99 % uptime
Today
Datacenter Routing and Switching Infrastructure Operational
90 days ago
99.99 % uptime
Today
Dedicated Servers Operational
90 days ago
99.99 % uptime
Today
Colocation Racks Operational
90 days ago
100.0 % uptime
Today
Facilites Operational
90 days ago
100.0 % uptime
Today
General Services Operational
90 days ago
100.0 % uptime
Today
Avoro CP & Support Operational
90 days ago
100.0 % uptime
Today
PHP-Friends CRM & Support Operational
90 days ago
100.0 % uptime
Today
Hotline Operational
90 days ago
100.0 % uptime
Today
Dedicated Control Panel Operational
90 days ago
100.0 % uptime
Today
IPMI VPN Operational
90 days ago
100.0 % uptime
Today
DDoS Manager Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Apr 24, 2026

No incidents reported today.

Apr 23, 2026

No incidents reported.

Apr 22, 2026
Completed - Symmetric filtering has been restored at 18:18. No further issues occured.
Apr 22, 19:02 CEST
Verifying - Full mitigation capacity has been restored without any issues. Symmetric filtering is yet to be restored.
Apr 22, 13:28 CEST
In progress - We will now restore the full capacity of our DDoS protection. Necessary cabling was already done this morning. No customer impact is expected.
Apr 22, 12:52 CEST
Verifying - The DDoS protection cluster has been back in normal operation since 01:33. As part of the analysis of the issue and the restoration of service, symmetric filtering remains temporarily disabled, as this was necessary to restore stable service. We strongly recommend that customers with access to the DDoS API leave it disabled until we have fully analyzed and resolved the situation. We currently expect to complete this tomorrow.
While work on the DDoS filters continues, redundancy and capacity remain reduced, but are sufficient for normal operation. We will update this post as soon as new information becomes available or further measures, maintenance, or restoration work are carried out. We will also provide a statement on today's issues.

Apr 22, 02:06 CEST
Update - After bringing the DDoS protection cluster back into service at 21:08, we received reports of minor issues affecting some IPs with symmetric filtering enabled. As a result, we took the DDoS protection cluster out of production again and are actively working on a permanent solution. IPs without symmetric filtering enabled, which make up the majority, were not affected, as our fix for the core issue has proven effective.
Apr 21, 21:26 CEST
Update - We are still working on restoring our DDoS protection cluster. Until then, attacks exceeding basic network-level protection cannot be fully mitigated. Basic protection remains in place all the time.
Apr 21, 20:30 CEST
Update - After reverting the update, we observed additional issues affecting some connections at 16:56 and 17:08, each lasting approximately 30 seconds. In response, we immediately removed the DDoS filters from production. Restoring DDoS protection services remains our highest priority.
Apr 21, 17:14 CEST
Update - After deploying the latest update, we observed issues affecting both established and new connections between 16:41 and 16:42.
We immediately rolled back the update to restore normal operation. We are currently investigating the root cause.

Apr 21, 16:50 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 21, 16:00 CEST
Scheduled - We will carry out maintenance on our DDoS protection infrastructure.

What we are doing
We will deploy software updates to our redundant DDoS 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 at any datacenter, but it cannot be ruled out entirely. Idle (inactive) connections and sessions may time out; active ones should not, as they are expected to remain 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 immediately. We will continue monitoring new tickets for a while after the maintenance.

Affected customers
All IP prefixes routed through our DDoS protection (which is the default) are affected by this maintenance. Only prefixes that have been explicitly configured to bypass our DDoS protection (which we do not recommend) are unaffected. In any case, no customer action is required.

Fallback plan
Should the update fail and cause issues, we will disconnect the filters within a few seconds and update this status post transparently. In that case, mitigation of attacks will not be possible for 30-60 minutes while we prepare a rollback.

Apr 21, 14:59 CEST
Apr 21, 2026

Unresolved incident: [firstcolo FRA4] Power Feed A on Generator Supply.

Apr 20, 2026
Completed - The scheduled maintenance has been completed.
Apr 20, 23:22 CEST
Update - Due to a bug in the new software release, we experienced minor traffic drop at approximately 21:57, 21:58, 21:59 lasting roughly 4–8 seconds.
Apr 20, 22:01 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 20, 21:00 CEST
Scheduled - We will carry out maintenance on our DDoS protection infrastructure.

What we are doing
We will deploy software updates to our redundant DDoS 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 at any datacenter, but it cannot be ruled out entirely. Idle (inactive) connections and sessions may time out; active ones should not, as they are expected to remain 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 immediately. We will continue monitoring new tickets for a while after the maintenance.

Affected customers
All IP prefixes routed through our DDoS protection (which is the default) are affected by this maintenance. Only prefixes that have been explicitly configured to bypass our DDoS protection (which we do not recommend) are unaffected. In any case, no customer action is required.

Fallback plan
Should the update fail and cause issues, we will disconnect the filters within a few seconds and update this status post transparently. In that case, mitigation of attacks will not be possible for 30-60 minutes while we prepare a rollback.

Apr 19, 20:44 CEST
Apr 19, 2026

No incidents reported.

Apr 18, 2026

No incidents reported.

Apr 17, 2026

No incidents reported.

Apr 16, 2026

No incidents reported.

Apr 15, 2026

No incidents reported.

Apr 14, 2026

No incidents reported.

Apr 13, 2026

No incidents reported.

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026

No incidents reported.