dataforest incident

Packet Loss via DTAG and DE-CIX

Minor Resolved View vendor source →

dataforest experienced a minor incident on February 20, 2026 affecting Edge Network (affects all locations), lasting 1d 2h. The incident has been resolved; the full update timeline is below.

Started
Feb 20, 2026, 04:27 PM UTC
Resolved
Feb 21, 2026, 06:34 PM UTC
Duration
1d 2h
Detected by Pingoru
Feb 20, 2026, 04:27 PM UTC

Affected components

Edge Network (affects all locations)

Update timeline

  1. identified Feb 20, 2026, 04:34 PM UTC

    The issue has been identified and a fix is being implemented.

  2. monitoring Feb 20, 2026, 04:48 PM UTC

    At 17:12 and 17:16, our monitoring systems alerted us about packet loss via our DTAG port. At 17:24, 17:27, and 17:31, our monitoring systems alerted us about packet loss via our DE-CIX port. Investigation showed high incoming traffic congesting these ports. We have immediately disabled our sessions with these providers for now and are analyzing the root cause to implement appropriate measures. Only traffic entering our network via DTAG or DE-CIX was affected by this issue, no other paths / uplinks were affected.

  3. resolved Feb 21, 2026, 06:34 PM UTC

    We are closing this incident, as the situation has been stable since this status post was created. The DE-CIX engineering team is still investigating yesterday's congestion affecting our peering port. Until further clarification, selected critical peering sessions remain disabled. Therefore we do not anticipate further issues with our DE-CIX peering. Inbound DTAG (Deutsche Telekom AG) traffic has been rerouted and will remain so until further notice to avoid similar situations. We will re-enable the remaining peering sessions once the root cause has been fully clarified with the DE-CIX team and the mitigation is in place. Only inbound traffic entering our network via DTAG or DE-CIX was affected for a few minutes till we disabled the sessions. All other uplinks/paths were not impacted. Outbound traffic was not affected.