Live / Seravo / Incident
Seravo: Availability issues in cluster fi-haarla
Seravo · seravo.comMinor incidentResolved2026-10-06 09:49 UTC
Public — what happened
Summary
Seravo reported availability problems affecting its fi-haarla cluster, which it classified as a minor incident, beginning at 06:11 UTC on 2026-10-06. The company said it was looking into the problem and, by 07:47 UTC, reported that a fix had been put in place and it was watching the results. Seravo did not say what caused the problem or which customers were affected. The incident was marked resolved at 09:49 on the same day.
Affected
fi-haarla cluster
Timeline
- Started — 2026-10-06 06:11 UTC
- Investigating — 2026-10-06 06:11 UTC
- Monitoring — 2026-10-06 07:47 UTC
- Resolved — 2026-10-06 09:49 UTC · 3h 37m 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 Seravo 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 Seravo: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Seravo report →
More from Seravo
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.