All Systems Operational
Uptime over the past 90 days. View historical uptime.
Interxion FRA8 ? Operational
90 days ago
99.98 % uptime
Today
Edge Network Operational
90 days ago
99.95 % uptime
Today
DDoS Protection Operational
90 days ago
99.99 % uptime
Today
Facilites ? Operational
90 days ago
100.0 % uptime
Today
maincubes FRA01 ? Operational
90 days ago
99.99 % uptime
Today
Core Network Operational
90 days ago
100.0 % uptime
Today
Virtual Servers Operational
90 days ago
99.96 % uptime
Today
Ceph Cluster ? Operational
90 days ago
100.0 % uptime
Today
Network Storage 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
99.96 % uptime
Today
TeamSpeak3 Servers Operational
90 days ago
99.99 % 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
Cloud Control Panel ? 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
Domain Robot ? 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.

No incidents or maintenance related to this downtime.

Past Incidents
Feb 13, 2025

No incidents reported today.

Feb 12, 2025

No incidents reported.

Feb 11, 2025

No incidents reported.

Feb 10, 2025

No incidents reported.

Feb 9, 2025

No incidents reported.

Feb 8, 2025
Emergency reboot of vps-002
Resolved - all affected VMs are booted up
Feb 8, 07:40 CET
Identified - we start all affected VMs on another node and expect that all VMs are fully booted up in about 15 minutes. Please note that the control of affected VMs is restricted during that time.
Feb 8, 07:26 CET
Update - We are continuing to investigate this issue.
Feb 8, 06:10 CET
Investigating - We currently investigate a outage of vps-002. Please note that no other node is affected.
Feb 8, 05:56 CET
Feb 7, 2025
E-Mail issues on web04.dataforest.net
Resolved - This incident has been resolved.
Feb 7, 16:00 CET
Monitoring - we identified the issue and deployed a fix and monitor the mail traffic
Feb 7, 14:35 CET
Investigating - We have received reports from customers who are unable to log into their existing mail accounts, while newly created mail accounts appear to be working. We are currently analyzing the issue and its impact, as it is not yet clear whether all mail services (IMAP, POP, SMTP) are affected. Please rest assured that no emails will be lost, as this is purely an accessibility issue.
Feb 7, 12:37 CET
Feb 6, 2025
Webhosting maintenance / web03 & web04
Completed - The scheduled maintenance has been completed.
Feb 6, 22:48 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 6, 22:00 CET
Scheduled - On the mentioned time, we will upgrade the operating system of the mentioned webhosting systems. During the maintenance work, we expect a maximum downtime of approx. 10 minutes per webhost.
Feb 1, 20:11 CET
Feb 5, 2025

No incidents reported.

Feb 4, 2025

No incidents reported.

Feb 3, 2025

No incidents reported.

Feb 2, 2025
Reboot of epyc9754-1, ts05.avoro.eu, ts15.avoro.eu, web03.dataforest.net
Resolved - As the hypervisor's load is fine now and no further issues occured, we are closing this incident.
Feb 2, 13:27 CET
Monitoring - All VMs have been booted. The performance of the hypervisor will be back to normal in a few minutes. Booting a large number of VMs causes high load, please refrain from manually rebooting your VMs as it will slow down the process overall.
Feb 2, 13:19 CET
Investigating - We identified web03.dataforest.net as another affected VM which will recover in the next 1-2 minutes.
Feb 2, 13:09 CET
Identified - The host system epyc9754-1, hosting customer VMs as well as the TS3 instances ts05.avoro.eu and ts15.avoro.eu, rebooted unexpectedly 5 minutes ago and is currently in progress of recovery.
Feb 2, 13:01 CET
Feb 1, 2025
Emergency Network Maintenance
Completed - The maintenance was successfully completed without any unforeseen issues or outages. During the individual line card reboots, minimal packet loss (~ 1%) occurred within a one- to two-second time frame, which was expected. Full redundancy and capacity have been restored.
Feb 1, 03:08 CET
In progress - During the preparation work currently in progress, we traced the root cause to a known Junos OS bug triggered by a routine commit operation related to the DDoS protection packet loss issue a few hours earlier (see https://status.dataforest.net/incidents/p27xf22kllpt).

Given the nature of the bug, we have decided not only to remove the specific configuration elements that triggered it during the upcoming maintenance window - this being the official workaround recommended by our vendor, Juniper Networks - but also to reboot all line cards and routing engines in the affected router as a precautionary measure.

Since all components are fully redundant, no service impact is expected. Should any unforeseen issues arise, we will immediately update this status post.

A software update that mitigates the bug will be implemented in the coming months during a separate maintenance window. For that update, the affected PoP will be fully drained of traffic beforehand to prevent any customer impact. As removing the problematic configuration resolves the immediate issue, this update, which requires additional preparation time, is no longer urgent.
Feb 1, 02:06 CET
Scheduled - Following a global increase in network latency (~200–400 ms) observed at 19:25 CET for approximately two minutes, we identified a malfunctioning Packet Forwarding Engine (PFE) in our active edge router. The router automatically disabled the faulty PFE, leading to an immediate recovery of services. Until its deactivation, traffic routed through the affected PFE experienced degradation.

Thanks to our redundant network architecture, no global outage occurred; however, latency-sensitive applications may have experienced severe delays.

During the upcoming maintenance window, we will reboot the line card hosting the affected PFE. This action is not expected to impact the network, but a residual risk remains.
Jan 31, 19:47 CET
Jan 31, 2025
Packet Loss at DDoS Protection
Resolved - This incident has been resolved.
Jan 31, 15:51 CET
Monitoring - Since the workaround has been applied, the situation is stable, however, this involves our DDoS protection being degraded while we work on a permanent solution. IPv4 addresses and prefixes without DDoS protection were not affected, IPv6 was also enirely unaffected.
Jan 31, 15:39 CET
Identified - Starting at 15:09 CET, we observed packet loss for IPv4 addresses under active mitigation / DDoS protection. The issue has been identified and workarounded at 15:14. We are working on a permanent fix.
Jan 31, 15:18 CET
Jan 30, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage