Live / Seravo / Incident
Seravo: Availability issues in cluster fi-frediksson
Seravo · seravo.comMinor incidentResolved2026-11-01 11:09 UTC
Public — what happened
Summary
Seravo reported availability problems affecting a server cluster named fi-frediksson, which it classed as a minor issue. The company said it began investigating at 10:06 UTC on 2026-11-01, and by 10:19 UTC it said it had found the problem and was working on a fix. At 10:30 UTC Seravo said a fix was in place and it was watching the results, and the incident had not been marked resolved. The company did not say who was affected or what caused the problem.
Affected
fi-fredriksson cluster
Timeline
- Started — 2026-11-01 10:06 UTC
- Investigating — 2026-11-01 10:06 UTC
- Identified — 2026-11-01 10:19 UTC
- Monitoring — 2026-11-01 10:30 UTC
- Resolved — 2026-11-01 11:09 UTC · 1h 03m 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 45, 2026, our weekly internet health report.