Live  /  Seravo  /  Incident

Seravo: Third party DNS problem

Seravo · seravo.comResolved2026-11-04 07:08 UTC
Public — what happened

Summary

Seravo said that starting at 05:15 UTC on 2026-11-04 a problem with an outside DNS provider left some websites unreachable or slow to respond. The company attributed the issue to that third party and said sites using Seravo's own DNS service were not affected. Seravo said affected sites would recover on their own once the provider fixed its problem, and the incident was marked resolved at 07:08.

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