Live / Incidents / dataforest
dataforest: Customer Feedback Requested on Individual Connectivity Issues
dataforest · dataforest.netImpact: minorResolved2026-08-30 12:59 UTC
Public — what happened
Summary
Between 1:00 and 2:00, we deployed an improved version of the previous fix for the TCP connection issue, providing better traffic distribution across our DDoS filters. The situation remains stable. As some further work is still required, we are keeping this incident open. During this work, the previous issue may briefly reoccur for a few minutes, affecting only a very small share of mostly outgoing connections (estimated <1%). The remaining work will be carried out tomorrow outside peak traffic hours.
Timeline
- Started — 2026-08-29 11:17 UTC
- Last update — 2026-08-30 12:59 UTC
- Resolved — 2026-08-31 21:33 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 seeCustomers 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 →