Live / Seravo / Incident
Seravo: Third party DNS problem
Seravo · seravo.comResolved2026-11-04 04:26 UTC
Public — what happened
Summary
Seravo said that starting at 21:24 UTC on 3 November 2026 it noticed a problem with an outside DNS provider, which left some websites unreachable or slow to respond. The company said the issue would clear up by itself once the provider fixed it, and that sites using Seravo's own DNS service were not affected. Seravo marked the incident resolved at 04:26 UTC on 4 November.
Timeline
- Started — 2026-11-03 21:24 UTC
- Identified — 2026-11-03 21:24 UTC
- Resolved — 2026-11-04 04:26 UTC · 7h 02m 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 46, 2026, our weekly internet health report.