DNSFilter Status
Real-time updates of DNSFilter issues and outages
DNSFilter status is Operational
Analytics
Front End UI
Domain Categorization
Active Incidents
No active incidents
Recently Resolved Incidents
We are currently investigating an issue in the DNSFilter UI that is preventing manual customers from seeing Roaming Client.
What Happened with Domain Categorization and System Load (e.g. msn.com ) -Some well-known domains like msn.com and started showing up as “uncategorized,” and our backend systems experienced a large spike in traffic. Here’s what we know:
What Happened: -Some websites like msn.com temporarily lost their category labels due to them being treated as uncategorized in the system. -Our platform automation tried to correct this but sent too many repeated requests at once, overloading internal systems. -This caused delays in restoring correct category information, so some domains stayed uncategorized longer than expected. -We’ve deployed a fix to reduce the load and are restoring normal behavior.
Key Customer Impact: -Domains like msn.com appeared uncategorized because they dropped out of cache and couldn’t be reloaded reliably. -This could affect content filtering accuracy, especially for high-traffic or policy-critical domains. -No DNS resolution outages occurred, but policy behavior may have been incorrect.
Fix: A fix has been implemented; however, due to caching, it may take 24–48 hours for affected domains to reflect the correct categorization.
Workaround: In the meantime, you can either add the impacted domains to your allow list or temporarily allow uncategorized domains within your policy settings to avoid disruption.
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.
DNSFilter Outage Survival Guide
DNSFilter Components
DNSFilter DNS1 Anycast Network
North America
South America
Europe
Asia
Africa
Oceania
DNSFilter DNS2 Anycast Network
North America
South America
Europe
Asia
Africa
Oceania
DNSFilter Dashboard
Analytics
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.
Front End UI
We are currently investigating an issue in the DNSFilter UI that is preventing manual customers from seeing Roaming Client.
API
DNSFilter Features
Interstitial Page
Blocked Page
Bypass Proxy
DoH Server
Changelog
Roaming Clients
Domain Categorization
What Happened with Domain Categorization and System Load (e.g. msn.com ) -Some well-known domains like msn.com and started showing up as “uncategorized,” and our backend systems experienced a large spike in traffic. Here’s what we know:
What Happened: -Some websites like msn.com temporarily lost their category labels due to them being treated as uncategorized in the system. -Our platform automation tried to correct this but sent too many repeated requests at once, overloading internal systems. -This caused delays in restoring correct category information, so some domains stayed uncategorized longer than expected. -We’ve deployed a fix to reduce the load and are restoring normal behavior.
Key Customer Impact: -Domains like msn.com appeared uncategorized because they dropped out of cache and couldn’t be reloaded reliably. -This could affect content filtering accuracy, especially for high-traffic or policy-critical domains. -No DNS resolution outages occurred, but policy behavior may have been incorrect.
Fix: A fix has been implemented; however, due to caching, it may take 24–48 hours for affected domains to reflect the correct categorization.
Workaround: In the meantime, you can either add the impacted domains to your allow list or temporarily allow uncategorized domains within your policy settings to avoid disruption.
