dataforest: Unreachable Prefixes

dataforest · dataforest.netImpact: majorResolved2026-09-26 23:50 UTC

Public — what happened

Summary

Reason for outage: After the recent edge router replacement at DRT-FRA8, some attack traffic was not distributed equally across both POPs for various reasons, and blackholing / prefix withdrawal was triggered for the mentioned prefixes. Our fixes applied shortly afterward have proven effective, and no further disruptions occurred despite ongoing attacks.

Timeline

Started — 2026-09-26 17:07 UTC
Last update — 2026-09-26 23:50 UTC
Resolved — 2026-09-26 23:50 UTC

Source of record: provider status page. Mirrored as reported; times in UTC.

With SquidGrid — where it starts on the route

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 →

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