Live  /  dataforest  /  Incident

dataforest: Outage of cloud01-fra01-ent, cloud03-fra01-ent, cloud10-fra01-ent

dataforest · dataforest.netMajor incidentResolved2026-11-07 19:22 UTC
Public — what happened

Summary

dataforest reported a major outage affecting three servers in its Frankfurt Entry product line: cloud01-fra01-ent, cloud03-fra01-ent and cloud10-fra01-ent. The company said it began investigating at 11:48 UTC on 2026-11-07, and a fix was in place and being monitored by 12:17 UTC. In a later update, dataforest said about 500 customer instances were affected to varying degrees, with storage errors on one server that it attributed to a network problem on that machine rather than its storage cluster, plus roughly five minutes of downtime on two others after crashes. It also said an additional five-minute outage on one server came from a human error during a restart, and that it knew of no file system damage; the incident was marked resolved at 19:22.

Affected

Virtual Servers

As listed on dataforest’s status page.

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 46, 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.