Historial de interrupciones de Webshrinker

1. 28 de septiembre de 2026 a las 12:51 UTCidentified

   Nuestro equipo de ingeniería ha identificado un problema que está causando que el dashboard no refleje los cambios correctamente dentro de la UI y actualmente está trabajando para implementar una solución para remediar el problema. Los cambios son activos y funcionan como se espera. Actualmente hay un retraso de hasta 30 minutos antes de que aparezcan en el panel de control, por lo que lo que estás viendo puede no reflejar las últimas actualizaciones todavía. Proporcionaremos estatus actualizado tan pronto como sea posible una vez que se haya implementado una solución.

2. 28 de septiembre de 2026 a las 14:35 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

3. 28 de septiembre de 2026 a las 15:29 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 28 de septiembre de 2026 a las 15:45 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de septiembre de 2026 a las 12:14 UTCinvestigating

   Nuestro equipo de ingeniería está investigando una cuestión que está causando que la resolución DNS sea intermitente en toda la región del Reino Unido y actualmente trabaja con nuestros asociados para resolver la situación.

2. 22 de septiembre de 2026 a las 12:26 UTCmonitoring

   La resolución está de vuelta y trabajando; la ingeniería está monitoreando.

3. 22 de septiembre de 2026 a las 14:26 UTCresolved

   Nuestra conectividad se proporciona a través de un intercambio de Internet (IX), esencialmente un centro compartido que nos conecta con muchas otras redes. Si nuestra propia conexión con la IX hubiera bajado, habría afectado a todos los clientes por igual, pero ese no era el caso aquí. Basándonos en lo que estamos viendo, es posible que un subconjunto de redes que comparten la misma infraestructura en el IX experimentó un problema localizado, lo que explicaría por qué sólo algunos clientes notaron un problema mientras que otros no. Queremos ser transparentes que esta es nuestra mejor teoría de trabajo en lugar de una causa de raíz confirmada, ya que no tenemos plena visibilidad en esa pieza específica de infraestructura. También hemos comprobado con nuestro proveedor de corriente, y han confirmado que todos los sistemas en su extremo se mostraron saludables durante este período. Seguiremos monitoreando de cerca, y te actualizaremos si aprendemos algo más. Por favor háganos saber si todavía está experimentando problemas.

Traducido automáticamente desde la actualización oficial del incidente.

1. 17 de septiembre de 2026 a las 20:35 UTCidentified

   Nuestro equipo ha identificado la cuestión que ha causado retrasos en la resolución del DNS y plazos. Engineering está trabajando activamente para implementar una solución para remediar y restaurar servicios. El estado actualizado se proporcionará lo antes posible. También puede mantenerse al día revisando nuestra página de estado aquí: https://status.dnsfilter.com/

2. 17 de septiembre de 2026 a las 20:47 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 17 de septiembre de 2026 a las 21:00 UTCresolved

   Hemos identificado la causa raíz de los problemas de latencia que afectan a ciertos clientes de la región de la Costa Oeste y hemos implementado una solución. El tráfico ha regresado a niveles estables, y el servicio funciona normalmente. Seguiremos vigilando de cerca la región para garantizar la estabilidad continua. Si sigues experimentando problemas, por favor contacta con nuestro equipo de Apoyo para la asistencia

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de septiembre de 2026 a las 16:22 UTCidentified

   Hemos identificado la causa de una cuestión que afecta a la presentación de informes. Los clientes pueden ser incapaces de cargar el DNS Query Log o ver retrasos al ver los datos del informe en el panel de control. Nuestro equipo está trabajando para una resolución completa. Si tiene alguna pregunta mientras tanto, póngase en contacto con nuestro Equipo de Apoyo. Vamos a proporcionar actualizaciones adicionales en breve.

2. 14 de septiembre de 2026 a las 16:48 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados

3. 14 de septiembre de 2026 a las 17:09 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 3 de junio de 2026 a las 17:56 UTCresolved

   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.

1. 28 de mayo de 2026 a las 13:46 UTCidentified

   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. 28 de mayo de 2026 a las 13:58 UTCmonitoring

   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. 28 de mayo de 2026 a las 16:47 UTCresolved

   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.

1. 11 de mayo de 2026 a las 14:37 UTCidentified

   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. 11 de mayo de 2026 a las 15:10 UTCresolved

   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.

1. 8 de mayo de 2026 a las 12:54 UTCidentified

   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. 8 de mayo de 2026 a las 16:11 UTCmonitoring

   We are continuing to monitor this issue.

3. 9 de mayo de 2026 a las 11:36 UTCresolved

   This incident has been resolved. Our cloud partner has resolved the issue impacting reporting performance. Functionality has now returned to normal operation.

1. 27 de abril de 2026 a las 11:09 UTCidentified

   Our engineering team has identified an issue where the dashboard may not show data in the DNS Query Log and is currently working to implement a fix to remediate the problem. We will provide updated status as soon as possible once a fix has been implemented.

2. 27 de abril de 2026 a las 12:47 UTCmonitoring

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

3. 27 de abril de 2026 a las 14:28 UTCresolved

   We’ve resolved the issue that was causing DNS Query Log data to not appear in the dashboard. Our engineering team identified the root cause and implemented a fix, and data visibility has now been restored.

1. 30 de marzo de 2026 a las 17:02 UTCidentified

   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. 30 de marzo de 2026 a las 17:26 UTCmonitoring

   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. 30 de marzo de 2026 a las 20:13 UTCresolved

   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.

1. 5 de diciembre de 2025 a las 9:15 UTCidentified

   Our engineering team has identified an issue with our cloud partner that may cause domains 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. 5 de diciembre de 2025 a las 9:37 UTCresolved

   The cloud partner has resolved the issue on their end. Our engineers have confirmed that both Anycast and DNSFilter APIs remained fully operational throughout the event.

1. 28 de noviembre de 2025 a las 14:23 UTCresolved

   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.

1. 18 de noviembre de 2025 a las 12:20 UTCinvestigating

   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. 18 de noviembre de 2025 a las 12:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 de noviembre de 2025 a las 12:26 UTCmonitoring

   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. 18 de noviembre de 2025 a las 15:49 UTCresolved

   This incident has been resolved.

1. 20 de octubre de 2025 a las 9:57 UTCidentified

   Our engineering team has identified an issue with our cloud partner that may cause the dashboard and API 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. 20 de octubre de 2025 a las 12:22 UTCresolved

   The cloud partner has resolved the issue on their end. Our engineers have confirmed that both Anycast and DNSFilter APIs remained fully operational throughout the event. No customer-facing impact or service degradation was observed.

1. 29 de septiembre de 2025 a las 15:02 UTCinvestigating

   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. 29 de septiembre de 2025 a las 18:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 de septiembre de 2025 a las 18:28 UTCmonitoring

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

4. 29 de septiembre de 2025 a las 20:51 UTCresolved

   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.

1. 2 de septiembre de 2025 a las 20:51 UTCidentified

   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. 5 de septiembre de 2025 a las 20:15 UTCresolved

   This incident has been resolved.

1. 29 de julio de 2025 a las 12:53 UTCresolved

   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

1. 22 de julio de 2025 a las 15:30 UTCresolved

   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.

1. 14 de julio de 2025 a las 12:14 UTCidentified

   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. 14 de julio de 2025 a las 12:45 UTCmonitoring

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

3. 14 de julio de 2025 a las 13:52 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 14 de julio de 2025 a las 17:04 UTCresolved

   This incident has been resolved.

5. 15 de julio de 2025 a las 13:12 UTCpostmortem

   **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.

1. 24 de junio de 2025 a las 15:56 UTCinvestigating

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

2. 24 de junio de 2025 a las 16:45 UTCmonitoring

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

3. 24 de junio de 2025 a las 18:40 UTCresolved

   This incident has been resolved.