DNSFilter Outage History

DNSFilter is up right now

DNSFilter had 26 outages in the last 2 years totaling 210h 38m of downtime — averaging 1.1 incidents per month.

There were 26 DNSFilter outages since September 26, 2024 totaling 210h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.dnsfilter.com

Major September 14, 2026

DNSFilter Reporting - Resolved

Detected by Pingoru
Sep 14, 2026, 04:22 PM UTC
Resolved
Sep 14, 2026, 05:09 PM UTC
Duration
47m
Affected: AnalyticsFront End UI
Timeline · 3 updates
  1. identified Sep 14, 2026, 04:22 PM UTC

    We have identified the cause of an issue affecting Reporting. Customers may be unable to load the DNS Query Log or see delays when viewing report data in the dashboard. Our team is working towards a full resolution. If you have any questions in the meantime, please contact our Support Team. We will be providing additional updates shortly.

  2. monitoring Sep 14, 2026, 04:48 PM UTC

    A fix has been implemented and we are monitoring the results

  3. resolved Sep 14, 2026, 05:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 3, 2026

Zorus - Data Availability Issue

Detected by Pingoru
Jun 03, 2026, 05:56 PM UTC
Resolved
Jun 03, 2026, 06:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 03, 2026, 05:56 PM UTC

    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.

Read the full incident report →

Minor May 28, 2026

DNSFilter - Investigating Incorrect Domain Classification

Detected by Pingoru
May 28, 2026, 01:46 PM UTC
Resolved
May 28, 2026, 04:47 PM UTC
Duration
3h
Affected: Domain Categorization
Timeline · 3 updates
  1. identified May 28, 2026, 01:46 PM UTC

    We are aware of an issue causing certain valid domains to be incorrectly classified as malicious. Our team has identified the cause and is actively implementing a rollback to restore normal classification behavior as quickly as possible. This issue does not impact DNSFilter DNS resolution or overall service availability. We will continue to provide updates as progress is made and expect to share another update shortly.

  2. monitoring May 28, 2026, 01:58 PM UTC

    We have implemented a rollback and are currently monitoring the environment to ensure domain classifications continue operating normally. This issue did not impact DNS resolution or overall DNSFilter service availability. We will continue to monitor closely and provide any additional updates if necessary. If you continue to experience any issues, please submit a support ticket.

  3. resolved May 28, 2026, 04:47 PM UTC

    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.

Read the full incident report →

Minor May 11, 2026

Investigating Dashboard & Insights Data Display Issues

Detected by Pingoru
May 11, 2026, 02:37 PM UTC
Resolved
May 11, 2026, 03:10 PM UTC
Duration
32m
Affected: Front End UI
Timeline · 2 updates
  1. identified May 11, 2026, 02:37 PM UTC

    Customers may experience issues with the Home Dashboard and Insights pages not displaying data. Additionally, the Site Deployment page may show a “Failed to Load QPS” error message. We have identified the root cause of the issue and are actively working on implementing a fix. DNS Resolution and Filtering are NOT affected.

  2. resolved May 11, 2026, 03:10 PM UTC

    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.

Read the full incident report →

Minor May 8, 2026

DNSFilter Dashboard Performance Issue - Identified

Detected by Pingoru
May 08, 2026, 12:54 PM UTC
Resolved
May 09, 2026, 11:36 AM UTC
Duration
22h 42m
Affected: Analytics
Timeline · 3 updates
  1. identified May 08, 2026, 12:54 PM UTC

    Our engineering team has identified an issue with our cloud partner that may cause the Reporting to have performance issues. Our Anycast network is unaffected as of this time. We will provide an updated status as soon as possible once the partner has resolved this issue.

  2. monitoring May 08, 2026, 04:11 PM UTC

    We are continuing to monitor this issue.

  3. resolved May 09, 2026, 11:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 30, 2026

DNS Resolution is (Down / Intermittent) - Resolved

Detected by Pingoru
Mar 30, 2026, 05:02 PM UTC
Resolved
Mar 30, 2026, 08:13 PM UTC
Duration
3h 11m
Affected: North AmericaNorth America
Timeline · 3 updates
  1. identified Mar 30, 2026, 05:02 PM UTC

    Our Engineering team has identified an issue that has caused DNS resolution failure observed in our NYC region and is actively working to implement a fix to remediate and restore services. Updated status will be provided as soon as possible.

  2. monitoring Mar 30, 2026, 05:26 PM UTC

    Traffic redirection has been completed, and we’ve shifted traffic to the closest available region. Performance should now be returning to normal, if it hasn’t stabilized already. We will continue to monitor closely to ensure stability.

  3. resolved Mar 30, 2026, 08:13 PM UTC

    This incident is now resolved. We have now shifted traffic back to the NYC region. This issue was identified to be caused by a routing problem at an upstream Internet Exchange provider, which impacted connectivity and cascaded to our services. To minimize customer impact, we temporarily rerouted traffic to our Washington, DC region. Once the issue was confirmed to be resolved by our upstream partner, traffic was safely restored to the NYC region.

Read the full incident report →

Notice November 28, 2025

Chromebook Roaming Client DoH Service

Detected by Pingoru
Nov 28, 2025, 02:23 PM UTC
Resolved
Nov 25, 2025, 08:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 28, 2025, 02:23 PM UTC

    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.

Read the full incident report →

Minor November 18, 2025

Dashboard Login Access Issues — Monitoring

Detected by Pingoru
Nov 18, 2025, 12:20 PM UTC
Resolved
Nov 18, 2025, 03:49 PM UTC
Duration
3h 29m
Affected: API
Timeline · 4 updates
  1. investigating Nov 18, 2025, 12:20 PM UTC

    Our engineering team is currently investigating an issue that is causing DNS resolution to be Intermittent and is currently working with our partners to implement a fix to resolve this problem. Updated status will be provided as soon as possible.

  2. investigating Nov 18, 2025, 12:26 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 18, 2025, 12:26 PM UTC

    We are currently investigating an issue affecting some users access to the DNSFilter dashboard. This does not impact DNS resolution. We are closely monitoring the situation and will provide updates as more information becomes available.

  4. resolved Nov 18, 2025, 03:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 29, 2025

Local Domains Resolving to Unknown Block Page

Detected by Pingoru
Sep 29, 2025, 03:02 PM UTC
Resolved
Sep 29, 2025, 08:51 PM UTC
Duration
5h 49m
Affected: Blocked Page
Timeline · 5 updates
  1. investigating Sep 29, 2025, 03:02 PM UTC

    We are currently investigating an issue impacting customers who have added local domains to their Local Domain List that are also publicly accessible. In these cases, users may experience problems when connecting to VPNs or other services, resulting in the Unknown Block Page being displayed. Our team is actively working to identify a permanent resolution. Further updates will be posted here as they become available.

  2. investigating Sep 29, 2025, 06:24 PM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 29, 2025, 06:27 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Sep 29, 2025, 06:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Sep 29, 2025, 08:51 PM UTC

    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.

Read the full incident report →

Major September 2, 2025

Zorus Portal Service Disruption

Detected by Pingoru
Sep 02, 2025, 08:51 PM UTC
Resolved
Sep 05, 2025, 08:15 PM UTC
Duration
2d 23h
Affected: Zorus PortalZorus Reporting
Timeline · 2 updates
  1. identified Sep 02, 2025, 08:51 PM UTC

    Status Report: Zorus Portal Service Disruption Summary We are currently experiencing a backend connectivity issue affecting several elements of the Zorus Portal. Core protection remains fully functional, but some portal features are impacted. Impacted Services The following portal features are temporarily unavailable or degraded: -Reporting: Issues with generating and sending reports. -Whitelabeling: Modifications to whitelabeling settings are unavailable. -Customer & Group Management: Creation of new customers and groups may fail. -Agent Downloads: Downloading the Zorus Agent is currently disrupted. -Gradient MSP Integration: Integration features are impacted. Unaffected Services Filtering and Protection: All core filtering and protection services remain operational and continue to protect end users without interruption.

  2. resolved Sep 05, 2025, 08:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 29, 2025

Degraded Performance – Zorus Policy Servers

Detected by Pingoru
Jul 29, 2025, 12:53 PM UTC
Resolved
Jul 25, 2025, 09:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 29, 2025, 12:53 PM UTC

    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

Read the full incident report →

Notice July 22, 2025

Zorus - Infrastructure Performance Degradation

Detected by Pingoru
Jul 22, 2025, 03:30 PM UTC
Resolved
Jul 21, 2025, 04:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 22, 2025, 03:30 PM UTC

    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.

Read the full incident report →

Major July 14, 2025

Dashboard Login Failure - Identified

Detected by Pingoru
Jul 14, 2025, 12:14 PM UTC
Resolved
Jul 14, 2025, 05:04 PM UTC
Duration
4h 50m
Affected: Front End UIAPIData Export
Timeline · 6 updates
  1. identified Jul 14, 2025, 12:14 PM UTC

    Our engineering team has identified an issue that is preventing users from logging into the dashboard and is currently working to implement a fix. We will provide updated status as soon as possible.

  2. monitoring Jul 14, 2025, 12:45 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jul 14, 2025, 01:04 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jul 14, 2025, 01:52 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jul 14, 2025, 05:04 PM UTC

    This incident has been resolved.

  6. postmortem Jul 15, 2025, 01:12 PM UTC

    **Dashboard Login Failure - Postmortem** **Summary:** The system experienced a performance reduction that resulted in slower API response times and an unresponsive front-end dashboard. As a result, users encountered delays when interacting with the dashboard and during API calls. **Resolution:** Our team identified the issue immediately and initiated an incident response. A hot fix addressing the root cause was developed, tested, and deployed the same day to restore normal service. **Next Steps:** We are conducting a deeper review of how our systems interact with the database to identify opportunities for long-term optimization and to prevent similar issues in the future.

Read the full incident report →

Minor June 24, 2025

UI Preventing Manual Customers from seeing the Roaming Client

Detected by Pingoru
Jun 24, 2025, 03:56 PM UTC
Resolved
Jun 24, 2025, 06:40 PM UTC
Duration
2h 44m
Affected: Front End UI
Timeline · 3 updates
  1. investigating Jun 24, 2025, 03:56 PM UTC

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

  2. monitoring Jun 24, 2025, 04:45 PM UTC

    A fix has been implemented and we are continuing to monitor the results.

  3. resolved Jun 24, 2025, 06:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 18, 2025

Temporary Query Log Disruption – No Impact to DNS Filtering

Detected by Pingoru
Jun 18, 2025, 01:29 PM UTC
Resolved
Jun 18, 2025, 01:29 PM UTC
Duration
—
Affected: Analytics
Timeline · 1 update
  1. resolved Jun 18, 2025, 01:29 PM UTC

    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.

Read the full incident report →

Major May 27, 2025

Dashboard Login Failure - Resolved

Detected by Pingoru
May 27, 2025, 01:47 PM UTC
Resolved
May 27, 2025, 05:09 PM UTC
Duration
3h 21m
Affected: Front End UI
Timeline · 4 updates
  1. investigating May 27, 2025, 01:47 PM UTC

    Our engineering team is currently investigating an issue that is preventing users from being able to log into the dashboard. We will provide updated status as soon as possible. DNS resolution is operating normally.

  2. monitoring May 27, 2025, 02:17 PM UTC

    We've implemented a fix and are now monitoring the results. Our investigation confirmed that this incident is tied to a third-party system, and we're currently engaging directly with their support team to achieve full resolution.

  3. monitoring May 27, 2025, 02:50 PM UTC

    The Third-party system that we are working with has identified and fixed the issue and they are currently in a monitoring state.

  4. resolved May 27, 2025, 05:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2025

Delays processing query log messaging

Detected by Pingoru
May 12, 2025, 08:10 AM UTC
Resolved
May 12, 2025, 11:04 AM UTC
Duration
2h 54m
Affected: Analytics
Timeline · 2 updates
  1. monitoring May 12, 2025, 09:32 AM UTC

    Between 08:10UTC and 08:30UTC we have experienced a network issue with one of our providers. We are currently working with them to understand what happened. The system has recovered and we are currently actively monitoring.

  2. resolved May 12, 2025, 11:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2025

Increased Latency in FRA region

Detected by Pingoru
May 07, 2025, 04:48 PM UTC
Resolved
May 07, 2025, 07:26 PM UTC
Duration
2h 38m
Affected: EuropeEurope
Timeline · 2 updates
  1. monitoring May 07, 2025, 04:48 PM UTC

    We've identified the root cause of the recent performance degradation. We have implemented a fix for our affected servers from our provider to permanently resolve this issue. We will continue to monitor performance closely and provide further updates as soon as the additional memory is provisioned. Thank you for your patience as we work to ensure a stable and optimal experience.

  2. resolved May 07, 2025, 07:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 29, 2025

DNS Resolution is Down - Investigating - EMEA

Detected by Pingoru
Apr 29, 2025, 10:21 AM UTC
Resolved
Apr 29, 2025, 11:15 AM UTC
Duration
53m
Affected: EuropeEurope
Timeline · 5 updates
  1. investigating Apr 29, 2025, 10:17 AM UTC

    Our engineering team is currently investigating an issue that is causing DNS resolution to be down and is currently working to implement a fix to resolve this problem. Updated status will be provided as soon as possible.

  2. identified Apr 29, 2025, 10:21 AM UTC

    Between the hours of 09:08 UTC and 09:47 UTC we experienced a significant higher latency than normal on specific London nodes. This impacted DNS resolution for customers that were routed to the London nodes. We have identified and remediated the issue and are currently monitoring.

  3. monitoring Apr 29, 2025, 10:21 AM UTC

    We are currently monitoring the region affected.

  4. monitoring Apr 29, 2025, 10:27 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Apr 29, 2025, 11:15 AM UTC

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

Read the full incident report →

Minor April 7, 2025

Dashboard - Query Log processing delays

Detected by Pingoru
Apr 07, 2025, 06:57 PM UTC
Resolved
Apr 07, 2025, 11:23 PM UTC
Duration
4h 26m
Affected: AnalyticsFront End UI
Timeline · 3 updates
  1. investigating Apr 07, 2025, 06:57 PM UTC

    We are currently investigating reports of delays affecting the processing of Query Log reporting. We understand the importance of timely access to this information and are working diligently to identify the root cause and restore normal processing speeds. During this time, query log reporting visibility may be affected. We do not anticipate any data loss. This issue is isolated to Query Log reporting; other platform functions are not impacted.

  2. monitoring Apr 07, 2025, 07:50 PM UTC

    A fix has been implemented and we are currently monitoring the results.

  3. resolved Apr 07, 2025, 11:23 PM UTC

    This incident has now been resolved.

Read the full incident report →

Minor March 30, 2025

Anycast Network: DNS-2

Detected by Pingoru
Mar 30, 2025, 08:16 PM UTC
Resolved
Mar 31, 2025, 12:21 AM UTC
Duration
4h 5m
Affected: North AmericaEurope
Timeline · 3 updates
  1. investigating Mar 30, 2025, 08:16 PM UTC

    We understand the recent DNS resolution disruptions may have caused inconvenience, and we sincerely apologize for any impact this has had on your operations. Please know maintaining a reliable service is a top priority for us, and we are actively working to resolve these issues as quickly as possible. On March 30th, 2025, starting at 18:10 UTC, our systems detected traffic intended for our service via DNS2 was unexpectedly being routed to our servers handling traffic over DNS1. While we are currently investigating the cause of this misrouting, we want to assure you that we are not observing any increase in latency at this time. Our team is engaged to examine this issue and implement a solution. We recognize the importance of keeping you informed and will provide further updates as soon as they are available. Thank you for your patience and understanding as we work diligently to restore optimal service.

  2. monitoring Mar 30, 2025, 09:52 PM UTC

    We have identified the cause of the issue where traffic intended for our service via DNS2 is unexpectedly being routed to our DNS1 servers, which began on March 30th, 2025, at 18:10 UTC. We are now monitoring the implementation of the solution. While investigating the initial misrouting, we currently observe no increase in latency. Further updates on the resolution will be provided as they become available. Thank you for your patience.

  3. resolved Mar 31, 2025, 12:21 AM UTC

    This incident has now been resolved.

Read the full incident report →

Minor March 26, 2025

MFA Prompted for re-setup

Detected by Pingoru
Mar 26, 2025, 05:52 PM UTC
Resolved
Mar 26, 2025, 09:07 PM UTC
Duration
3h 15m
Affected: Front End UI
Timeline · 3 updates
  1. investigating Mar 26, 2025, 05:52 PM UTC

    Date of Incident: Mar 25, 2025 Time: 2PM UTC Affected Systems/Services: MFA Incident Priority Level: Medium Description: We are currently investigating reports of users being prompted to re-setup their Multi-Factor Authentication (MFA) in order to access the dashboard. This is not intended behavior, and we understand the inconvenience it causes. Impact: Users may be unable to access the dashboard without re-setting up their MFA. This issue affects users utilizing MFA for login. There are no impacts to security policies. Current Status: Our engineering team is actively investigating the root cause of this unexpected MFA re-setup request. We are working to identify and implement a solution as quickly as possible. We are monitoring system logs and authentication services.

  2. monitoring Mar 26, 2025, 05:56 PM UTC

    A fix has been implemented and we are now monitoring the results. Thank you for your understanding.

  3. resolved Mar 26, 2025, 09:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 24, 2025

API Delays

Detected by Pingoru
Mar 24, 2025, 04:42 PM UTC
Resolved
Mar 24, 2025, 07:32 PM UTC
Duration
2h 50m
Affected: API
Timeline · 2 updates
  1. investigating Mar 24, 2025, 04:42 PM UTC

    Affected Systems/Services: Dashboard/API Incident Priority Level: Medium Summary: This announcement is to inform you that we are currently investigating delayed API responses on the Dashboard and API that began at 12:17 UTC on March 24, 2025. There is no impact on Anycast nodes and DNS resolutions. We have stabilized the system and we are monitoring the situation. We understand the potential impact this may have and are working diligently to identify and resolve the delays as quickly as possible. We will provide further updates on our progress as they become available Thank you for your patience and understanding.

  2. resolved Mar 24, 2025, 07:32 PM UTC

    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.

Read the full incident report →

Major November 27, 2024

Costa Rica: Scheduled Reboot Error

Detected by Pingoru
Nov 27, 2024, 08:54 PM UTC
Resolved
Nov 22, 2024, 12:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 27, 2024, 08:54 PM UTC

    Date of incident: 11/22/2024 Affected Systems/Services: Anycast Network/DNS Resolution Incident Priority Level: High Summary: On Nov 22, 2024 a critical service on the anycast node in Costa Rica experienced an issue after a scheduled reboot, resulting in the unavailability of DNSFilter services during this period. Customers utilizing our Costa Rica node were unable to perform DNS requests, which impacted their service quality. Upon discovering the issue, our engineering teams acted swiftly to reroute services and restore full functionality. To prevent similar incidents in the future, our team has enhanced monitoring capabilities and instituted additional checks during system reboots. These measures aim to improve the reliability of our services and ensure we can quickly detect and address potential issues. We appreciate the understanding of our customers as we continue to strengthen our systems.

Read the full incident report →