Telephone System Migration
Update - According to our telephony provider, the earlier service disruption of our hotline has been resolved. We have been able to confirm this in initial tests.

We do not know exactly when our telephone availability was first affected, but based on the information currently available, we assume that the disruption began at around 10:11. According to our telephony provider, normal service had been restored by 11:48 at the latest.

Our planned migration to the new platform has not yet taken place.
Sep 01, 2026 - 12:01 CEST
Update - Independently of the planned migration, our telephony provider is currently experiencing a major service disruption. As a result, our telephone availability may currently be impaired.

At this time, we do not know whether the current outage is related to the planned migration of our account. If you need to contact us, please use a ticket or email.
Sep 01, 2026 - 11:18 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 01, 2026 - 00:00 CEST
Scheduled - Our telephone system is expected to be migrated to a new technical platform by our telephony provider in the early morning hours of September 1, 2026.

We have prepared for the migration and tested the new platform in advance. Nevertheless, temporary limitations to our telephone availability cannot be completely ruled out during a migration of this kind.

Our ticket systems will remain available as usual throughout the migration.

If you experience any issues when trying to reach us by phone, please contact us via ticket or email. In addition to the reason for your call, please include a detailed description of the issue you encountered, the exact time of the call, and the phone number you called from. This information will help us investigate any potential issues with our telephone system as quickly as possible.

We will keep you updated here on the progress of the migration.
Sep 1, 2026 00:00 - Sep 2, 2026 23:59 CEST
dataforest Network Operational
Edge Network (affects all locations) Operational
DDoS Protection (affects all locations) Operational
Dedicated Servers (EQX-FR4 & DRT-FRA8) Operational
Datacenter MC-FRA01 Operational
Datacenter Core Routing & Switching Operational
Ceph Cluster Operational
Virtual Servers Operational
Dedicated Servers Operational
Plesk Web Hosting Operational
TeamSpeak3 Servers Operational
Network Storage Operational
Facilites Operational
Datacenter FC-FRA4 Operational
Datacenter Core Routing & Switching Operational
Dedicated Servers Operational
Facilites Operational
General Services Under Maintenance
Avoro CP & Support Operational
PHP-Friends CRM & Support Operational
Hotline Under Maintenance
Dedicated Control Panel Operational
IPMI VPN Operational
DDoS Manager Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

DDoS Protection Software Update Sep 3, 2026 15:30-17:30 CEST

We will carry out maintenance on our DDoS protection infrastructure.

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

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

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

Fallback plan
Should the update fail and cause issues, we will disconnect the respective filters within a few seconds.
Posted on Sep 01, 2026 - 11:23 CEST
Sep 2, 2026
Partial Outage of Avoro VMs and Control Panel Functionality
Resolved - VNC access was restored at 22:37, followed by the reinstallation feature at 01:00. All previously affected control panel functionality has now been restored.
Thank you for bearing with us while we worked to restore these services.
Sep 2, 01:10 CEST
Update - Basic control panel functionality was restored at 18:50, including starting and stopping VMs as well as booting from mounted ISOs. Creating and restoring backups is also possible again.
We are continuing to work on restoring VNC access and the reinstallation feature.
Sep 1, 19:44 CEST
Monitoring - All affected VMs have been back online on replacement hardware for the past 10 minutes. Restoration was completed in well under 30 minutes, significantly faster than the previously estimated recovery time of up to two hours.
We are now working to restore the control panel functionality.
Sep 1, 13:38 CEST
Identified - Two of our Avoro VM hosts, epyc7513-1 and epyc9374f-8, are currently experiencing an outage. The majority of Avoro VMs are not affected by the host outage itself. Customers can check the customer area to see whether any of their VMs are running on the affected hosts.

VM control functions such as starting, stopping, and reinstalling are currently unavailable for all Avoro customers, as this functionality depends on the affected hosts.

Affected VMs will be restarted on replacement hardware as soon as possible. We expect this process to take up to two hours. Individual VMs may be restored significantly earlier, as they will be brought back online sequentially.

We will share further details as soon as they become available.
Sep 1, 13:01 CEST
Sep 1, 2026

Unresolved incident: Telephone System Migration.

Aug 31, 2026
Customer Feedback Requested on Individual Connectivity Issues
Resolved - This incident has been resolved.
Aug 31, 23:16 CEST
Update - Between 1:00 and 2:00, we deployed an improved version of the previous fix for the TCP connection issue, providing better traffic distribution across our DDoS filters. The situation remains stable. As some further work is still required, we are keeping this incident open. During this work, the previous issue may briefly reoccur for a few minutes, affecting only a very small share of mostly outgoing connections (estimated <1%). The remaining work will be carried out tomorrow outside peak traffic hours.
Aug 30, 14:59 CEST
Monitoring - Our fix has proven effective. TeamSpeak 3 traffic has been stable since 23:20.
Aug 30, 00:45 CEST
Identified - We have received reports of occasional packet loss affecting some TeamSpeak 3 servers over the past few minutes. We have already identified the root cause, which by design only affects traffic entering our network via our DRT-FRA8 PoP (~ 50% of the total traffic). We are working on a fix.
Aug 29, 23:10 CEST
Monitoring - We have received and analyzed customer feedback and applied a configuration change within our backbone that may improve the stability of (very few) TCP connections previously affected by timeouts or resets. We are monitoring the situation and continue to welcome feedback on whether the change has improved the affected connections.
Aug 29, 19:00 CEST
Update - If you are experiencing an issue that appears network-related but the MTR does not show any latency or packet loss, please still send us the MTR together with a reliable way to reproduce the actual problem.
We need both to compare the affected path and to verify the issue itself. This can be any reproducible test, for example an SSH connection that times out or guest access to an affected application or monitoring system.
Aug 29, 15:32 CEST
Investigating - Since our Edge Router Replacement at EQX-FR4, we have received a small number of reports about increased latency or timeouts when reaching certain providers. Specifically:

• Vodafone: We identified congestion between one of our transit providers (Tata Communications) and Vodafone during peak traffic hours. Following our maintenance, traffic was automatically routed over this path instead of the previously used one. While the maintenance triggered this routing change, the underlying congestion was outside our network and unrelated to the maintenance itself. After the first reports, we adjusted our routing yesterday to avoid the affected path. Traffic to Vodafone is now using an unaffected alternative route. Our Smokeping reflects both the issue and the subsequent improvement.

• netcup: We do not see any latency issues in our Smokeping. However, we have received at least two reports today about timeouts when accessing services hosted with netcup. We are currently analyzing the issue.

Our request: If you notice anything unusual, such as latency spikes or timeouts, please reach out to our support team so we can investigate individual issues. If possible, please include an MTR in both directions (dataforest -> external network and external network -> dataforest), so that we can compare reports and identify common patterns.
Aug 29, 13:17 CEST
Aug 30, 2026
DDoS Protection Software Update
Completed - The scheduled maintenance has been completed.
Aug 30, 16:15 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 30, 15:15 CEST
Scheduled - We will carry out maintenance on our DDoS protection infrastructure.

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

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

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

Fallback plan
Should the update fail and cause issues, we will disconnect the respective filters within a few seconds.
Aug 29, 22:49 CEST
Aug 29, 2026
Aug 28, 2026
Network Maintenance: Edge Router Replacement at EQX-FR4
Completed - The scheduled maintenance has been completed.
Aug 28, 04:44 CEST
Verifying - Phase 2 has been completed. Over the next few hours, we'll migrate remaining transit providers to the new router and take care of cleanup and documentation.
Aug 28, 02:49 CEST
Update - Phase 1 has been completed with less than one minute of downtime for local EQX-FR4 customers. We are now working on internal connectivity between EQX-FR4 and the rest of the dataforest network (Phase 2, BGP customers shall keep their sessions shut down).
Aug 28, 02:01 CEST
Update - Phase 1 has started.
Aug 28, 01:52 CEST
Update - Preparatory and validation work is complete. In 15 minutes, we will disconnect EQX-FR4 from dataforest's internal network, followed shortly thereafter by its disconnection from the internet. This will mark the start of Phase 1, as described previously.
Aug 28, 01:22 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 27, 22:00 CEST
Scheduled - On the night of August 27th to 28th, in the timeframe 22:00 - 07:00 (CEST), we are upgrading our PoP EQX-FR4.

We will replace our Juniper MX304 router with a new Juniper PTX10008, which will be our new standard platform for edge routers. This makes our backbone future-proof and allows us to significantly increase capacity at a PoP simply by adding line cards, without the need for further router replacements. Keep an eye on our Instagram, where we will share behind-the-scenes insights of the new hardware setup soon!

Who is affected:
Directly affected (downtime): All BGP, IP Transit, and dedicated server customers connected locally at EQX-FR4 (identifiable by the server's hostname).
Indirectly affected (no downtime): All other customers at all dataforest locations. You will experience no outage, but temporary reroutings will occur for some of our peering connections. Those can result in slightly increased latency, but we do not anticipate any outage as all traffic and DDoS protection is handled by our secondary PoP DRT-FRA8. Our backbone capacity is halved but always sufficient. As usual, a residual risk remains when working on critical backbone infrastructure even after intensive lab-testing of the new setup.

Maintenance schedule & impact for EQX-FR4:
• Phase 1 (30-60 minutes): Hard downtime for all local connections at EQX-FR4 during physical migration. Servers at this location will be unreachable.
• Phase 2 (30-60 minutes): General internet connectivity is restored. However, internal network connectivity from EQX-FR4 to the rest of the dataforest network will remain temporarily unavailable while routing protocols (iBGP/MPLS) are being migrated.
• Fallback Plan: In the highly unlikely event of a critical failure at our secondary PoP before the new PTX router is fully operational, we will immediately abort the migration and restore service via the existing MX router within ~30 minutes. The same goes for any production issues with the new router.

Customer action suggested (EQX-FR4 only):
• BGP & IP Transit: Please actively reroute upstream traffic away from your sessions for the entire maintenance window to avoid blackholing during Phase 2 or preparation work.
• High-Availability Workloads: We strongly recommend temporarily draining affected nodes from your global load balancing prior to the maintenance.

We will keep you updated here on the progress. Thank you for your cooperation!
Aug 24, 01:26 CEST
Aug 27, 2026
[Action Required] FC-FRA4: Power Maintenance on Sub-Distribution UV-O
Completed - The scheduled maintenance has been completed.
Aug 27, 18:00 CEST
Verifying - We have successfully verified all servers and found no issues. All affected servers have now been back online for more than 30 minutes. The maintenance has therefore been completed well ahead of schedule.
If your server is not reachable, please verify your server's console output via IPMI in the Dedicated Server Control Panel and resolve any software-side issues that may prevent the system from booting. If you suspect a hardware fault, please contact our support team via ticket.
Aug 27, 16:02 CEST
Update - All rack feeds were re-energized faster than planned, within approximately 5 minutes. No racks required servers to be powered on individually due to high inrush current.
The first affected servers are already back online. Any servers that do not power on on their own will be checked by us automatically. Please do not interfere with this process manually!
Aug 27, 15:31 CEST
Update - Power on UV-O has been restored. We are now sequentially re-energizing all affected rack feeds, which is expected to take up to 30 minutes. Afterwards, we will report any racks that require servers to be powered on individually due to high inrush current.
Aug 27, 15:24 CEST
Update - UV-O is now off.
Aug 27, 13:35 CEST
Update - Final reminder: Single-PSU servers connected to UV-O must be shut down now.
Aug 27, 13:20 CEST
In progress - Preparatory work on the power sub-distribution is currently underway. The scheduled shutdown of UV-O has been moved to 13:30, and the timeline has been adjusted accordingly.
Reminder: Single-PSU servers connected to UV-O must be shut down cleanly before 13:30 CEST.
Aug 27, 11:52 CEST
Scheduled - On August 27, 2026, maintenance work will take place in the FC-FRA4 data center on power sub-distribution UV-O, which will be migrated to the new low-voltage main distribution (NSHV-B) in the process. This measure is part of the step-by-step modernization of the power supply at the site. In the target state, every dataforest rack will be supplied via NSHV-A and NSHV-B, each equipped with its own UPS and emergency power generator system, which further increases redundancy.

Who is affected:

Some dedicated servers and colocation racks at the FC-FRA4 location are affected. Other locations are not affected.

For servers with redundant power supplies (according to contract / product description), no outage is expected. If these are located in affected racks, only one power feed will drop out. Depending on CPU and load, a lower maximum clock speed is possible.

Servers with only one power supply connected to UV-O will be without power during the maintenance and must be cleanly shut down by you beforehand to prevent data loss and file system damage. We will shut down affected Managed Dedicated Servers.

How to check if your server is affected:

Check your server's current name at https://dedicated.dataforest.cloud. If your server carries the suffix "-UV-O", for example "root1234.fc-fra4-UV-O", it is directly affected. Please note that there are also other sub-distribution suffixes that have nothing to do with this maintenance.

Maintenance schedule (CEST):

• Morning: Multi-hour preparation of the new supply line from NSHV-B to UV-O.
• 13:30: Scheduled shutdown of UV-O.
• 15:30: Power restoration of UV-O and sequential energizing of all rack feeds including functionality check.
• 16:00: Expected completion of feed energization.
• until approx. 16:30: Buffer for racks with high inrush current (step-by-step "server-by-server" switching on may be required). We will inform you here continuously about affected racks.
• 16:30 – 17:30: On-site inspection of servers that did not power on automatically.

You must shut down affected servers yourself prior to 13:00. Otherwise, they will be hard switched off by the power shutdown.

Servers start automatically with our standard BIOS configuration after power supply is restored. Servers that do not switch on automatically will be checked by our technicians independently and immediately. Please do not intervene manually in this process!

The maintenance window serves as a guideline. Work on the power supply is subject to strict safety precautions: Before switching over, the new supply line will be extensively electrically tested (including insulation and impedance measurement, testing of the clockwise rotating field, and phase position control). Personnel safety takes precedence over schedule adherence at all times. We will inform you here about the progress of the work and any deviations.

Which racks are affected:

Dedicated Server Racks:
X06, X12, Y01, Y02, Y03, Y04, Y05, Y06, Y07, Y08, Y10, Y11, Y12

Colocation / Customer Racks:
X17, Y13, Y14, Y15

Additionally, for the duration of the maintenance work, there is no power redundancy for the core switching of rack rows Y and Z. Network operation in rack row X is unaffected by this.

You can assign your server's rack using the switch port statistics. For customer racks, we have no knowledge about the power redundancy of the connected servers. Colocation customers must explicitly connect redundant servers to PDUs of different sub-distribution boards.

How you should prepare:

• Subscribe to this status page for live updates.
• Check if your server is connected to "-UV-O".
• Plan the shutdown and downtime if necessary.
• Inform your users or customers.
• If possible, perform a test reboot in advance and check whether all required services start automatically.
• Check via IPMI whether "Restore on AC Power Loss -> Power On" is set in the BIOS (dataforest standard). Our support will carry out this check upon request until August 26, 2026.
• Check RAID and backups and create a full backup before the maintenance.

If your server is not reachable after the maintenance:

First check this status post. Is the maintenance completed and no problem reported for your rack? Then please check the screen output via IPMI in the control panel and resolve any software problems that prevent starting. If you suspect a hardware defect, contact our support via ticket system.

How dataforest is prepared:

• Top-of-rack switches are redundantly connected to power and network. Even with only one booked uplink, your switch has two power feeds and two core switch uplinks ("double redundancy").
• Our on-site spare parts warehouse is being stocked up to resolve potential defects quickly.
• dataforest employees are on site and coordinate the work directly with the service providers.
• Redundant power supplies were checked in advance.

Thank you for your assistance.
Aug 19, 01:41 CEST
DE-CIX Frankfurt Peering
Completed - The scheduled maintenance has been completed.
Aug 27, 03:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 26, 23:00 CEST
Scheduled - The internet exchange DE-CIX has announced maintenance on its Frankfurt peering platform.

When our own port is affected by such maintenance, we gracefully reroute the affected traffic in advance. Our port is not affected by this maintenance, so no action is required from our side.

Please note: DE-CIX Frankfurt is one of the world's largest internet exchanges. Other networks affected by the maintenance may not reroute their traffic in advance, potentially causing connectivity issues on paths to or from dataforest even though our own network remains fully operational.

We have seen this during previous DE-CIX maintenance windows and publish this notice as a precaution. Such issues occur outside our control and cannot be prevented or resolved by us.
Aug 26, 22:38 CEST
Aug 26, 2026
DE-CIX Frankfurt Peering
Completed - The scheduled maintenance has been completed.
Aug 26, 05:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 25, 23:00 CEST
Scheduled - The internet exchange DE-CIX has announced maintenance on its Frankfurt peering platform, directly affecting our port at DE-CIX Frankfurt.

Beforehand, we will gracefully reroute traffic that would normally be exchanged via DE-CIX Frankfurt to other peering platforms (MegaIX and ERA-IX) or transit providers.

This may result in slightly increased latency on some paths, but we do not expect any outage.

Please note: DE-CIX Frankfurt is one of the world's largest internet exchanges. While we will reroute our traffic in advance, other networks may not do so, potentially causing connectivity issues outside our control. We have seen this during previous DE-CIX maintenance windows and cannot prevent or resolve such issues ourselves.
Aug 25, 22:53 CEST
Aug 25, 2026
Aug 24, 2026

No incidents reported.

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

Aug 21, 2026

No incidents reported.

Aug 20, 2026

No incidents reported.

Aug 19, 2026
DDoS Protection Maintenance
Completed - The scheduled maintenance has been completed.
Aug 19, 16:30 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 19, 15:30 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/sessions may time out; active ones should not, as they are synchronized during the startup of a new software release. If you notice anything unusual, such as timeouts of active sessions or the inability to connect to your server, please contact our support.

Affected customers
All IP prefixes routed through our DDoS protection (which is the default) 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 sophisticated attacks will not be possible for 30-60 minutes.
Aug 18, 16:05 CEST
← Incident History Powered by Atlassian Statuspage