Live / GoGuardian / Incident
GoGuardian: Degraded Performance: GoGuardian Admin – DNS Filtering
GoGuardian · goguardian.comMinor incidentResolved2026-09-11 03:50 UTC
Public — what happened
Summary
GoGuardian reported slowed performance in the DNS Filtering feature of GoGuardian Admin, beginning on 2026-09-10 at 18:54 UTC, and rated the incident minor. The company said service came back for affected users around 2:00 PM PDT. GoGuardian explained that after a September 8 incident it had boosted computing power on its DNS servers, but this event showed those servers also lacked enough network capacity for peak demand, so it added capacity and later shifted the system to larger infrastructure built for network traffic. The company said it was keeping watch on the feature, and the incident was marked resolved on 2026-09-12 at 02:57.
Timeline
- Started — 2026-09-10 18:54 UTC
- Resolved — 2026-09-12 02:57 UTC · 32h 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 GoGuardian 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 GoGuardian: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GoGuardian report →
More from GoGuardian
Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.