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

As listed on Seravo’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 Seravo 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 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.

The full archive is on the Seravo status & history page.

Related: Seravo status & history. SquidGrid is not affiliated with Seravo.