Live  /  dataforest  /  Incident

dataforest: Unreachable Prefixes

dataforest · dataforest.netMajor incidentResolved2026-09-26 23:50 UTC
Public — what happened

Summary

dataforest reported a major incident on 2026-09-26 in which certain network address ranges (prefixes) could not be reached, beginning at 17:07 UTC. The company said that following a recent swap of an edge router at its DRT-FRA8 site, incoming attack traffic was not split evenly between its two points of presence, which led to those prefixes being blackholed or withdrawn. dataforest said fixes it put in place soon after worked, and that no further interruptions happened even though the attacks continued. The incident was marked resolved at 23:50.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach dataforest against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for dataforest: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the dataforest report →

More from dataforest

Covered in The Squid’s Ink, Week 40, 2026, our weekly internet health report.

The full archive is on the dataforest status & history page.

Related: dataforest status & history. SquidGrid is not affiliated with dataforest.