Webshrinker Outage History

Webshrinker is up right now

Webshrinker had 12 outages in the last 2 years totaling 114h 58m of downtime — averaging 0.5 incidents per month.

There were 12 Webshrinker outages since July 14, 2025 totaling 114h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.webshrinker.com

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. Our cloud partner has resolved the issue impacting reporting performance. Functionality has now returned to normal operation.

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 →