DNSFilter Outage History

Our connectivity is provided through an Internet Exchange (IX), essentially a shared hub that connects us with many other networks. If our own connection to the IX had gone down, it would have affected all customers equally, but that wasn't the case here. Based on what we're seeing, it's possible that a subset of networks sharing the same infrastructure at the IX experienced a localized issue, which would explain why only some customers noticed a problem while others didn't. We want to be transparent that this is our best working theory rather than a confirmed root cause, as we don't have full visibility into that specific piece of infrastructure. We also checked with our upstream provider, and they've confirmed that all systems on their end showed as healthy throughout this period. We're continuing to monitor closely, and we'll update you if we learn anything further. Please let us know if you're still experiencing any issues.

We’ve identified the root cause of the latency issues affecting certain customers in the West Coast region and have implemented a fix. Traffic has returned to stable levels, and the service is operating normally. We will continue to closely monitor the region to ensure continued stability. If you continue to experience issues, please reach out to our Support team for assistance

This incident has been resolved.

On June 3, 2026 between 6:47:00 and 6:53:00 UTC, some historical query data (older than ~2 weeks) was temporarily unavailable. Scheduled and queried reports that ran during this window may have returned zero or partial results. DNS filtering and traffic ingestion were not affected at any point. The issue has been resolved. If you have any questions please reach out to our Support team.

The issue causing certain domains to be incorrectly classified as malicious has been fully resolved. Our team implemented a rollback and completed monitoring to confirm classification behavior has returned to normal operation. This issue did not impact DNS resolution or overall DNSFilter service availability. We sincerely apologize for the disruption and appreciate your patience while we worked to quickly identify and resolve the issue. If you continue to experience any related problems, please reach out to our Support team for further assistance.

The issue impacting the Home Dashboard and Insights pages, as well as the “Failed to Load QPS” error message on the Site Deployment page, has been resolved. Functionality has returned to normal operation. If you continue to experience any issues, please reach out to our Support team for further assistance.

This incident has been resolved.

An issue was identified affecting our DoH service that may have impacted customers in the London region. This did NOT affect DNS1/DNS2 UDP/TCP/TLS/DoT services. We identified the fault on Tuesday the 25th and resolved the it by 20:00 UTC by updating all affected servers. In addition, we have improved our monitoring and automation by adding a new failsafe to avoid this from happening again in the future.

This incident has been resolved.

A solution has been implemented, and performance has returned to normal. No further impact is expected. If you continue to experience related issues, please reach out directly to our Support team.

This incident has been resolved.

Between 5:22 AM and 9:03 AM EST, we observed degraded performance on our policy servers. The issue was identified and resolved, and systems have since returned to normal operation. Components Affected: Zorus - Policy Servers

Incident Summary: Between 12:37 PM and 2:25 PM EST on July 21, 2025, we experienced degraded performance affecting portions of our infrastructure, including the portal, reporting, and policy management. Resolution: Additional resources have been provisioned to improve performance and ensure better handling of system load moving forward.

This incident has been resolved.

This incident has been resolved.

Between hour 5 to 6 UTC today, a networking issue outside of our control was detected between our AnyCast nodes across the world and our query log eventing system. DNS Resolution and Filtering were NOT affected. The networking issue has since been resolved but as a result you might notice that on a daily basis, about 2% less query log entries than a usual weekday in our Query Log. We are working with our networking partners to ensure this does not happen again and we are putting extra safeguards in place to avoid this in the future.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

The issue is now resolved. Post-Mortem to follow.

This incident has now been resolved.

This incident has now been resolved.

This incident has been resolved.

UPDATE: We have remediated the delayed API responses to the Dashboard and API. Our systems are stable and operating as normal and therefore the incident is being declared as closed. We are continuously monitoring our systems ensuring that there are no potential impacts to our customers. Thank you for your understanding.