Is GoGuardian Down?

We have resolved the issue causing delayed reports on Smart Alerts, which users may have experienced between 11:32 AM ET and 1:50 PM ET. Service has been fully restored. We apologize for any trouble caused by this issue. --- [2026-10-22T11:09:09.786-07:00] (monitoring) We implemented a fix to resolve issues with Smart Alerts reports in GoGuardian Admin, and service has been restored for most customers. We will continue to monitor performance to ensure full functionality. We apologize for any trouble caused by this issue. --- [2026-10-22T10:17:44.072-07:00] (identified) Since about 11:32 AM ET on October 22, some Smart Alerts reports have been slow to process, and some may not have been delivered. We've found the cause, and we're putting a fix in place now. Some reports submitted during this time may have been lost. We'll post another update within an hour or as soon as we know more.

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 was successful. 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. --- [2026-09-10T20:50:06.503-07:00] (monitoring) 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. --- [2026-09-10T11:54:30.349-07:00] (investigating) 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.

This incident has been resolved. Impact: Between approximately 12:00 PM and 2:10 PM PDT on September 8, a subset of GoGuardian Admin DNS Filtering users experienced delayed or failed DNS resolution. Current status: Service returned to normal at approximately 2:10 PM PDT on September 8, and we have observed stability since that time. What we've done: To help prevent this from happening again, our engineering teams have updated the DNS Filtering service infrastructure to better handle unexpected increases in request activity. What's next: Our team is continuing to make improvements to the performance of the DNS Filtering system, and we are keeping a close watch on the service in the meantime. We sincerely apologize for the disruption this caused. --- [2026-09-08T15:02:30.871-07:00] (monitoring) Functionality has been restored for affected users. We are actively monitoring the GoGuardian Admin DNS Filtering service and continuing to investigate the root cause of the issue. --- [2026-09-08T12:40:44.237-07:00] (investigating) We are continuing to investigate this issue. --- [2026-09-08T12:40:15.221-07:00] (investigating) As of approximately 12:00 PM PDT, we have seen an increase in reports of delayed and/or failed resolution time 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.