Degraded Performance: GoGuardian Admin – DNS Filtering

Update timeline

1. investigating Sep 10, 2026, 06:54 PM UTC

   As of approximately 11:29 AM PDT, we have seen an increase in reports of delayed and/or failed resolution times within GoGuardian Admin DNS Filtering. Our team is currently working to resolve this issue and will keep you updated as we implement a fix. We sincerely apologize for any inconvenience.

2. monitoring Sep 11, 2026, 03:50 AM UTC

   Functionality has been restored for affected users as of approximately 2:00 PM PDT. After the September 8 incident, we increased compute on the existing DNS servers. Today's issue showed we also needed much more network capacity to handle peak query volume. We added capacity to restore service. We have since moved the DNS edge onto larger, network-optimized infrastructure. We are actively monitoring GoGuardian Admin DNS Filtering. We sincerely apologize for the disruption.

3. resolved Sep 12, 2026, 02:55 AM UTC

   After the resolution released yesterday, we have monitored our DNS traffic, our systematic monitoring tools and our Customer Support channels to identify any issues and we are confident that the resolution has been released. However, a handful of districts have reached out with lingering issues due to old requests remaining in the DNS cache. If you experience any issues like this, we wanted to provide the troubleshooting steps. Please see the steps below. To force your device to fetch updated network routes immediately, we recommend performing the quick DNS reset steps below. 1) Restart your web browser or test the site in an Incognito / Private window. 2) Flush your local DNS cache: a)Windows: Open Command Prompt, type 'ipconfig /flushdns', and press Enter. b) Mac: Open Terminal, type 'sudo dscacheutil -flushcache', and press Enter. c) If using Chrome: Paste 'chrome://net-internals/#dns' into your address bar and click 'Clear host cache'. Alternatively, if you are seeing this issue across multiple endpoints on the same network, your local recursive resolvers, firewalls, or edge gateways may be caching the stale record. To fix: 1) Please flush your local DNS server caches (e.g., Clear-DnsServerCache in PowerShell or rndc flush for BIND) 2) Restart any network hardware acting as a DNS proxy, or 3) Temporarily forward upstream queries to public resolvers (1.1.1.1 or 8.8.8.8) to bypass lingering ISP-level cache. We greatly apologize for the significant inconvenience and greatly appreciate the patience of those impacted. Feel free to reach out to Customer Support with any additional issues at https://docs.goguardian.com/welcome.