GoGuardian Incident History

1. monitoringSep 11 · 03:50 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.

Reported by GoGuardian on their status page.

1. resolvedSep 9 · 22:20 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.

Reported by GoGuardian on their status page.

1. resolvedSep 4 · 17:02 UTC

   The service disruption has been fully resolved. System performance has returned to normal, and all services should now be functioning as expected. Thank you for your patience, and we apologize for any inconvenience caused.

Reported by GoGuardian on their status page.

1. resolvedSep 2 · 21:10 UTC

   This incident has been resolved.

Reported by GoGuardian on their status page.