Live  /  Providers  /  dataforest

dataforest

dataforest.netNo open incidents

Independent assessment — SquidGrid is not affiliated with dataforest. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks dataforest’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what dataforest is reporting

Current & recent incidents

Resolved

Unreachable Prefixes

Major impact · 2026-09-26 23:50 UTC

Resolved

Temporary Packet Loss at EQX-FR4 PoP

Major impact · 2026-09-25 03:52 UTC

Resolved

Partial Packet Loss via DDoS Protection

Major impact · 2026-09-14 18:50 UTC

Resolved

Partial Outage of Avoro VMs and Control Panel Functionality

Major impact · 2026-09-01 20:24 UTC

Resolved

Customer Feedback Requested on Individual Connectivity Issues

Minor impact · 2026-08-30 12:59 UTC

Mirrored from the provider’s own published status. Times in UTC.

Independent path health

A status page tells you what dataforest has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

dataforest runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of dataforest is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with dataforest.