dataforest incident
Increased latency at the firstcolo FRA4 location
dataforest experienced a minor incident on January 14, 2026 affecting Datacenter Core Routing & Switching, lasting 5h 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 14, 2026, 01:11 PM UTC
We are currently experiencing increased latency at our firstcolo FRA4 location in Frankfurt. There is no packet loss.
- monitoring Jan 14, 2026, 01:17 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 14, 2026, 06:33 PM UTC
Yesterday, some physical links at our Equinix PoP flapped. While these flaps caused no customer impact, they led to an imbalance between internal links connecting our new Equinix PoP and our core PoP at Interxion. Increased bandwidth usage during the day resulted in critical utilization on one port, which required immediate correction. During the initial corrective change, one port at our firstcolo FRA4 location became saturated at 14:03, causing increased latency for some customers (without packet loss). At 14:15, a further adjustment was applied, successfully and permanently resolving the issue. Additional configuration changes were implemented over the following hours to prevent similar imbalances within our new MPLS environment in the event of link flaps. We are still investigating the root cause of the link flaps at Equinix. As redundancy is fully in place and the balancing issue has been resolved, we do not expect any further impact.