Histórico de interrupções do Webshrinker

1. 28 Gwengolo 2026 da 12:51 UTCidentified

   Nossa equipe de engenharia identificou um problema que está fazendo com que o painel não reflita as mudanças corretamente dentro da UI e atualmente está trabalhando para implementar uma correção para corrigir o problema. As mudanças são ativas e funcionam como esperado. Atualmente, há um atraso de até 30 minutos antes de aparecerem no painel, então o que você está vendo pode não refletir as últimas atualizações ainda. Nós forneceremos o status atualizado assim que possível uma vez que uma correção tenha sido implementada.

2. 28 Gwengolo 2026 da 14:35 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

3. 28 Gwengolo 2026 da 15:29 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 28 Gwengolo 2026 da 15:45 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gwengolo 2026 da 12:14 UTCinvestigating

   Nossa equipe de engenharia está atualmente investigando uma questão que está fazendo com que a resolução do DNS seja intermitente em toda a região do Reino Unido e atualmente está trabalhando com nossos parceiros para resolver a situação.

2. 22 Gwengolo 2026 da 12:26 UTCmonitoring

   A resolução está de volta e a trabalhar; a engenharia está a monitorizar.

3. 22 Gwengolo 2026 da 14:26 UTCresolved

   Nossa conectividade é fornecida através de um Internet Exchange (IX), essencialmente um hub compartilhado que nos conecta com muitas outras redes. Se a nossa ligação com o IX tivesse caído, teria afectado todos os clientes igualmente, mas não foi o caso aqui. Com base no que estamos vendo, é possível que um subconjunto de redes compartilhando a mesma infraestrutura no IX tenha experimentado um problema localizado, o que explicaria por que apenas alguns clientes perceberam um problema enquanto outros não. Queremos ser transparentes de que esta é a nossa melhor teoria de trabalho em vez de uma causa raiz confirmada, uma vez que não temos total visibilidade para essa peça específica de infra-estrutura. Também conferimos com o nosso fornecedor a montante, e eles confirmaram que todos os sistemas do seu lado mostraram-se saudáveis durante todo este período. Continuamos a monitorizar de perto e atualizamos-te se soubermos mais alguma coisa. Por favor, avise-nos se ainda tiver problemas.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gwengolo 2026 da 20:35 UTCidentified

   Nossa equipe identificou o problema que causou latência e tempo de resolução do DNS. A engenharia está trabalhando ativamente para implementar uma correção para corrigir e restaurar serviços. O status atualizado será fornecido o mais rapidamente possível. Você também pode acompanhar as atualizações revisando nossa página de status aqui: https://status.dnsfilter.com/

2. 17 Gwengolo 2026 da 20:47 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 17 Gwengolo 2026 da 21:00 UTCresolved

   Identificamos a causa básica dos problemas de latência que afetam certos clientes na região da Costa Oeste e implementamos uma correção. O tráfego voltou a níveis estáveis, e o serviço está a funcionar normalmente. Continuaremos a acompanhar de perto a região, a fim de garantir a continuação da estabilidade. Se você continuar a experimentar problemas, por favor, entre em contato com nossa equipe de suporte para assistência

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gwengolo 2026 da 16:22 UTCidentified

   Identificámos a causa de um problema que afecta o relatório. Os clientes podem não ser capazes de carregar o DNS Consulta Log ou ver atrasos ao visualizar os dados do relatório no painel. A nossa equipa está a trabalhar para uma resolução completa. Se você tiver alguma dúvida, entre em contato com nossa Equipe de Suporte. Vamos fornecer atualizações adicionais em breve.

2. 14 Gwengolo 2026 da 16:48 UTCmonitoring

   Uma correção foi implementada e estamos monitorando os resultados

3. 14 Gwengolo 2026 da 17:09 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Mezheven 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 16:11 UTCmonitoring

   We are continuing to monitor this issue.

3. 9 Mae 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 12:47 UTCmonitoring

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

3. 27 Ebrel 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 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 Kerzu 2025 da 09: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 Kerzu 2025 da 09: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 Du 2025 da 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 Du 2025 da 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 Du 2025 da 12:26 UTCinvestigating

   We are continuing to investigate this issue.

3. 18 Du 2025 da 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 Du 2025 da 15:49 UTCresolved

   This incident has been resolved.

1. 20 Here 2025 da 09: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 Here 2025 da 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 Gwengolo 2025 da 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 Gwengolo 2025 da 18:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 Gwengolo 2025 da 18:28 UTCmonitoring

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

4. 29 Gwengolo 2025 da 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 Gwengolo 2025 da 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 Gwengolo 2025 da 20:15 UTCresolved

   This incident has been resolved.

1. 29 Gouere 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 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 Gouere 2025 da 12:45 UTCmonitoring

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

3. 14 Gouere 2025 da 13:52 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 14 Gouere 2025 da 17:04 UTCresolved

   This incident has been resolved.

5. 15 Gouere 2025 da 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 Mezheven 2025 da 15:56 UTCinvestigating

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

2. 24 Mezheven 2025 da 16:45 UTCmonitoring

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

3. 24 Mezheven 2025 da 18:40 UTCresolved

   This incident has been resolved.