Historique des pannes de Webshrinker

1. 28 septembre 2026 à 12:51 UTCidentified

   Notre équipe d'ingénierie a identifié un problème qui fait que le tableau de bord ne reflète pas correctement les changements au sein de l'assurance-chômage et travaille actuellement à la mise en oeuvre d'une correction pour remédier au problème. Les changements sont actifs et fonctionnent comme prévu. Il y a actuellement un délai de 30 minutes avant qu'ils ne apparaissent dans le tableau de bord, donc ce que vous voyez peut ne pas refléter les dernières mises à jour. Nous fournirons un état actualisé dès que possible une fois qu'une correction aura été mise en œuvre.

2. 28 septembre 2026 à 14:35 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

3. 28 septembre 2026 à 15:29 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 28 septembre 2026 à 15:45 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 septembre 2026 à 12:14 UTCinvestigating

   Notre équipe d'ingénieurs enquête actuellement sur un problème qui fait que la résolution DNS est intermittente dans toute la région du Royaume-Uni et travaille actuellement avec nos partenaires pour résoudre la situation.

2. 22 septembre 2026 à 12:26 UTCmonitoring

   La résolution revient et fonctionne; l'ingénierie est la surveillance.

3. 22 septembre 2026 à 14:26 UTCresolved

   Notre connectivité est assurée par un échange Internet (IX), essentiellement un hub partagé qui nous relie à de nombreux autres réseaux. Si notre propre connexion avec le IX avait diminué, cela aurait affecté tous les clients également, mais ce n'était pas le cas ici. Sur la base de ce que nous voyons, il est possible qu'un sous-ensemble de réseaux partageant la même infrastructure au IX ait connu un problème localisé, ce qui expliquerait pourquoi seulement certains clients ont remarqué un problème alors que d'autres ne l'ont pas fait. Nous voulons être transparents sur le fait qu'il s'agit de notre meilleure théorie de travail plutôt que d'une cause fondamentale confirmée, car nous n'avons pas toute la visibilité sur ce morceau d'infrastructure spécifique. Nous avons également vérifié avec notre fournisseur en amont, et ils ont confirmé que tous les systèmes à leur fin ont montré la santé pendant toute cette période. Nous continuons à surveiller de près, et nous vous mettrons à jour si nous apprenons quelque chose de plus. Veuillez nous faire savoir si vous rencontrez encore des problèmes.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 17 septembre 2026 à 20:35 UTCidentified

   Notre équipe a identifié le problème qui a causé la latence de résolution DNS et des délais. L'ingénierie travaille activement à la mise en oeuvre d'un correctif pour réparer et restaurer les services. Un état actualisé sera fourni dès que possible. Vous pouvez également suivre les mises à jour en consultant notre page de statut ici: https://status.dnsfilter.com/

2. 17 septembre 2026 à 20:47 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

3. 17 septembre 2026 à 21:00 UTCresolved

   Nous avons identifié la cause profonde des problèmes de latence touchant certains clients de la région de la côte Ouest et avons mis en place une solution. Le trafic est revenu à des niveaux stables, et le service fonctionne normalement. Nous continuerons de surveiller de près la région afin d'assurer la stabilité. Si vous continuez à éprouver des problèmes, veuillez contacter notre équipe de soutien pour obtenir de l'aide

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 14 septembre 2026 à 16:22 UTCidentified

   Nous avons identifié la cause d'un problème touchant les rapports. Les clients peuvent ne pas être en mesure de charger le journal de requêtes DNS ou voir les retards lors de la visualisation des données de rapport dans le tableau de bord. Notre équipe travaille à une résolution complète. Si vous avez des questions entre-temps, veuillez contacter notre équipe de soutien. Nous fournirons des mises à jour supplémentaires sous peu.

2. 14 septembre 2026 à 16:48 UTCmonitoring

   Une correction a été mise en œuvre et nous suivons les résultats

3. 14 septembre 2026 à 17:09 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 3 juin 2026 à 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 mai 2026 à 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 mai 2026 à 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 mai 2026 à 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 mai 2026 à 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 mai 2026 à 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 mai 2026 à 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 mai 2026 à 16:11 UTCmonitoring

   We are continuing to monitor this issue.

3. 9 mai 2026 à 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 avril 2026 à 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 avril 2026 à 12:47 UTCmonitoring

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

3. 27 avril 2026 à 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 mars 2026 à 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 mars 2026 à 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 mars 2026 à 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 décembre 2025 à 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 décembre 2025 à 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 novembre 2025 à 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 novembre 2025 à 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 novembre 2025 à 12:26 UTCinvestigating

   We are continuing to investigate this issue.

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

   This incident has been resolved.

1. 20 octobre 2025 à 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 octobre 2025 à 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 septembre 2025 à 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 septembre 2025 à 18:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 septembre 2025 à 18:28 UTCmonitoring

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

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

   This incident has been resolved.

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

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

3. 14 juillet 2025 à 13:52 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 14 juillet 2025 à 17:04 UTCresolved

   This incident has been resolved.

5. 15 juillet 2025 à 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 juin 2025 à 15:56 UTCinvestigating

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

2. 24 juin 2025 à 16:45 UTCmonitoring

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

3. 24 juin 2025 à 18:40 UTCresolved

   This incident has been resolved.