Go Guardian incident

Degraded Performance: GoGuardian Admin – DNS Filtering

Resolved after 1 day 2 hours, affecting DNS Filtering, on September 8, 2026.

resolved Sep 09, 2026, 10:20 PM UTC

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.

Started
Sep 08, 2026, 07:40 PM UTC
Resolved
Sep 09, 2026, 10:20 PM UTC
Duration
1d 2h
Detected by Pingoru
Sep 08, 2026, 07:40 PM UTC

Affected components

DNS Filtering

Update timeline

  1. investigating Sep 08, 2026, 07:40 PM UTC

    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.

  2. investigating Sep 08, 2026, 07:40 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 08, 2026, 10:02 PM UTC

    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.

  4. resolved Sep 09, 2026, 10:20 PM UTC

    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.

Your product runs on more than Go Guardian

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →