Live / dataforest / Incident
dataforest: Customer Feedback Requested on Individual Connectivity Issues
dataforest · dataforest.netMinor incidentResolved2026-08-30 12:59 UTC
Public — what happened
Summary
dataforest reported a minor incident, starting on 2026-08-29 at 11:17 UTC, involving TCP connection problems that some individual customers experienced, and asked affected users for feedback. The company said it rolled out a refined version of an earlier fix between 1:00 and 2:00, which it described as spreading traffic more evenly across its DDoS filters, and that conditions had since been stable. It kept the incident open for further work planned outside busy hours, warning that the problem could briefly return for a few minutes and touch an estimated fewer than 1% of connections, mostly outgoing ones. The incident was still listed as being monitored, with a resolution time recorded as 2026-08-31 at 21:33.
Timeline
- Started — 2026-08-29 11:17 UTC
- Resolved — 2026-08-31 21:33 UTC · 2 days after it started
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 →
More from dataforest