Webshrinker had 27 outages in the last 2 years totaling 210h 7m of downtime — averaging 1.1 incidents per month.
There were 27 Webshrinker outages since June 19, 2024 totaling 210h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
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.
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.
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.
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.
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.
We are continuing to monitor this issue.
This incident has been resolved. Our cloud partner has resolved the issue impacting reporting performance. Functionality has now returned to normal operation.
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.
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.
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.
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.
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.
We are continuing to investigate this issue.
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.
This incident has been resolved.
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.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
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.
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.
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.
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.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.
**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.
We are currently investigating an issue in the DNSFilter UI that is preventing manual customers from seeing Roaming Client.
A fix has been implemented and we are continuing to monitor the results.
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.
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.
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.
The Third-party system that we are working with has identified and fixed the issue and they are currently in a monitoring state.
This incident has been resolved.
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.
This incident has been resolved.
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.
This incident has been resolved.
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.
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.
We are currently monitoring the region affected.
We are continuing to monitor for any further issues.
The issue is now resolved. Post-Mortem to follow.
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.
A fix has been implemented and we are currently monitoring the results.
This incident has now been resolved.
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.
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.
This incident has now been resolved.
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.
A fix has been implemented and we are now monitoring the results. Thank you for your understanding.
This incident has been resolved.
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.
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.
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.
We want to inform you about a current situation that may affect your service experience. DNSFilter services are 100% available, however, one of our Internet Exchange (IX) providers in the DC region is experiencing an outage. As a result, some network traffic is being rerouted through our servers in Chicago and NYC. This unexpected shift in traffic may lead to an increase in latency as these servers handle the additional load. Please know that our technical teams are working diligently with the IX provider to resolve the issue as quickly as possible. We are committed to maintaining the performance and reliability of our network services and will keep you updated as we work through this challenge. We apologize for any inconvenience this may cause and appreciate your patience and understanding. If you have any further questions or need assistance, please don't hesitate to reach out to our support team. Thank you for trusting us with your service needs.
We are continuing to investigate this issue.
We are pleased to inform you, this issue has now been resolved and all DNSFilter services are operating normal. We appreciate our understanding during this incident. Our team is ensuring reliable services, and we are continuously monitoring the network to detect and prevent similar issues in the future. Thank you for your trust in us.