DNSFilter status is Operational

Tue 17
Wed 18
Thu 19
Fri 20
Sat 21
Sun 22
Mon 23
now
Analytics
Tue 17
Wed 18
Thu 19
Fri 20
Sat 21
Sun 22
Mon 23
now
Front End UI
Tue 17
Wed 18
Thu 19
Fri 20
Sat 21
Sun 22
Mon 23
now
Domain Categorization
Tue 17
Wed 18
Thu 19
Fri 20
Sat 21
Sun 22
Mon 23
now
Last updated 1 minute ago from official status page. Learn more
Stay ahead of DNSFilter outages
Sign up to create a custom dashboard to monitor the services you rely on. 3,000+ services supported.

Active Incidents

No active incidents

Recently Resolved Incidents

UI Preventing Manual Customers from seeing the Roaming Client
Started 24 Jun 2025 15:56:19 (8 hours ago), resolved 24 Jun 2025 18:40:28 (5 hours ago)
Minor Incident
Resolved
Front End UI

We are currently investigating an issue in the DNSFilter UI that is preventing manual customers from seeing Roaming Client.

Domain Categorization & System Load
Started 20 Jun 2025 17:07:43 (4 days ago), resolved 23 Jun 2025 12:51:04 (1 day ago)
Incident without Impact
Resolved
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.

Temporary Query Log Disruption – No Impact to DNS Filtering
Started 18 Jun 2025 13:29:05 (6 days ago), resolved 18 Jun 2025 13:29:05 (6 days ago)
Incident without Impact
Resolved
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.

DNSFilter Outage Survival Guide

A step-by-step guide to help you survive a DNSFilter outage
NaN%

    DNSFilter Components

    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now

    DNSFilter DNS1 Anycast Network

    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    North America
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    South America
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Europe
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Asia
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Africa
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Oceania
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now

    DNSFilter DNS2 Anycast Network

    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    North America
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    South America
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Europe
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Asia
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Africa
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Oceania
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now

    DNSFilter Dashboard

    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Analytics
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Temporary Query Log Disruption – No Impact to DNS Filtering
    Started 18 Jun 2025 13:29:05 (6 days ago), resolved 18 Jun 2025 13:29:05 (6 days ago)
    Incident without Impact
    Resolved
    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
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    UI Preventing Manual Customers from seeing the Roaming Client
    Started 24 Jun 2025 15:56:19 (8 hours ago), resolved 24 Jun 2025 18:40:28 (5 hours ago)
    Minor Incident
    Resolved
    Front End UI

    We are currently investigating an issue in the DNSFilter UI that is preventing manual customers from seeing Roaming Client.

    API
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now

    DNSFilter Features

    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Interstitial Page
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Blocked Page
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Bypass Proxy
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    DoH Server
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Changelog
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Roaming Clients
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Domain Categorization
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Domain Categorization & System Load
    Started 20 Jun 2025 17:07:43 (4 days ago), resolved 23 Jun 2025 12:51:04 (1 day ago)
    Incident without Impact
    Resolved
    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.

    Dynamic DNS Updater
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now

    DNSFilter Webshrinker

    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Webshrinker API
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Webshrinker Dashboard
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Webshrinker Categorization Engine
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now

    DNSFilter Zorus

    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Zorus Portal
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Zorus Reporting
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now
    Zorus Policy Servers
    Tue 17
    Wed 18
    Thu 19
    Fri 20
    Sat 21
    Sun 22
    Mon 23
    now