Webshrinker Outage History

Started Sep 28, 2026, 12:51 PM UTC· resolved Sep 28, 2026, 03:45 PM UTC

1. identified Sep 28, 2026, 12:51 PM UTC

   Our engineering team has identified an issue that is causing the dashboard to not reflect changes correctly within the UI and is currently working to implement a fix to remediate the problem. The changes made are active and are working, just not being displayed correctly. We will provide updated status as soon as possible once a fix has been implemented.

2. identified Sep 28, 2026, 02:35 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Sep 28, 2026, 03:29 PM UTC

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

4. resolved Sep 28, 2026, 03:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 22, 2026, 12:14 PM UTC· resolved Sep 22, 2026, 02:26 PM UTC

1. investigating Sep 22, 2026, 12:14 PM UTC

   Our engineering team is currently investigating an issue that is causing DNS resolution to be Intermittent across the UK region and is currently working with our partners to resolve the situation.

2. monitoring Sep 22, 2026, 12:26 PM UTC

   Resolution is back in and working; engineering is monitoring.

3. resolved Sep 22, 2026, 02:26 PM UTC

   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.

Read the full incident report →

Started Sep 17, 2026, 08:35 PM UTC· resolved Sep 17, 2026, 09:00 PM UTC

1. identified Sep 17, 2026, 08:35 PM UTC

   Our team has identified the issue that has caused DNS resolution latency and timeouts. Engineering is actively working to implement a fix to remediate and restore services. Updated status will be provided as soon as possible. You can also keep up with updates by reviewing our status page here: https://status.dnsfilter.com/

2. monitoring Sep 17, 2026, 08:47 PM UTC

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

3. resolved Sep 17, 2026, 09:00 PM UTC

   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

Read the full incident report →

Started Sep 14, 2026, 04:22 PM UTC· resolved Sep 14, 2026, 05:09 PM UTC

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 →

Started Jun 03, 2026, 06:30 AM UTC· resolved Jun 03, 2026, 06:30 AM UTC

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 →

Started May 28, 2026, 01:46 PM UTC· resolved May 28, 2026, 04:47 PM UTC

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 →

Started May 11, 2026, 02:37 PM UTC· resolved May 11, 2026, 03:10 PM UTC

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 →

Started Nov 25, 2025, 08:00 PM UTC· resolved Nov 25, 2025, 08:00 PM UTC

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 →

Started Nov 18, 2025, 12:20 PM UTC· resolved Nov 18, 2025, 03:49 PM UTC

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 →

Started Sep 29, 2025, 03:02 PM UTC· resolved Sep 29, 2025, 08:51 PM UTC

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 →

Started Sep 02, 2025, 08:51 PM UTC· resolved Sep 05, 2025, 08:15 PM UTC

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 →

Started Jul 25, 2025, 09:00 AM UTC· resolved Jul 25, 2025, 02:03 PM UTC

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 →

Started Jul 21, 2025, 04:30 PM UTC· resolved Jul 21, 2025, 07:25 PM UTC

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 →

Started Jul 14, 2025, 12:14 PM UTC· resolved Jul 14, 2025, 05:04 PM UTC

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 →

Started Jun 24, 2025, 03:56 PM UTC· resolved Jun 24, 2025, 06:40 PM UTC

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 →

Started Jun 20, 2025, 05:07 PM UTC· resolved Jun 23, 2025, 12:51 PM UTC

1. monitoring Jun 20, 2025, 05:07 PM UTC

   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.

2. resolved Jun 23, 2025, 12:51 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 18, 2025, 01:29 PM UTC· resolved Jun 18, 2025, 01:29 PM UTC

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 →

Started May 27, 2025, 01:47 PM UTC· resolved May 27, 2025, 05:09 PM UTC

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 →

Started May 12, 2025, 08:10 AM UTC· resolved May 12, 2025, 11:04 AM UTC

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 →

Started May 07, 2025, 04:48 PM UTC· resolved May 07, 2025, 07:26 PM UTC

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 →

Started Apr 29, 2025, 10:17 AM UTC· resolved Apr 29, 2025, 11:15 AM UTC

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 →

Started Apr 07, 2025, 06:57 PM UTC· resolved Apr 07, 2025, 11:23 PM UTC

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 →

Started Mar 30, 2025, 08:16 PM UTC· resolved Mar 31, 2025, 12:21 AM UTC

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 →

Started Mar 26, 2025, 05:52 PM UTC· resolved Mar 26, 2025, 09:07 PM UTC

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 →

Started Mar 24, 2025, 04:42 PM UTC· resolved Mar 24, 2025, 07:32 PM UTC

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 →