Störungsverlauf von Webshrinker

1. 28. September 2026 um 12:51 UTCidentified

   Unser Engineering-Team hat ein Problem identifiziert, das dazu führt, dass das Dashboard Änderungen innerhalb der Benutzeroberfläche nicht korrekt widerspiegelt, und arbeitet derzeit daran, einen Fix zu implementieren, um das Problem zu beheben. Veränderungen sind aktiv und funktionieren wie erwartet. Es gibt derzeit eine Verzögerung von bis zu 30 Minuten, bevor sie im Dashboard angezeigt werden, so dass das, was Sie sehen, möglicherweise noch nicht die neuesten Updates widerspiegelt. Wir werden den aktualisierten Status so schnell wie möglich bereitstellen, sobald ein Fix implementiert wurde.

2. 28. September 2026 um 14:35 UTCidentified

   Wir arbeiten weiter an einer Lösung für dieses Problem.

3. 28. September 2026 um 15:29 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 28. September 2026 um 15:45 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. September 2026 um 12:14 UTCinvestigating

   Unser Engineering-Team untersucht derzeit ein Problem, das dazu führt, dass die DNS-Auflösung intermittierend in der gesamten britischen Region ist, und arbeitet derzeit mit unseren Partnern zusammen, um die Situation zu lösen.

2. 22. September 2026 um 12:26 UTCmonitoring

   Die Auflösung ist wieder da und funktioniert; Engineering ist Monitoring.

3. 22. September 2026 um 14:26 UTCresolved

   Unsere Konnektivität wird über einen Internet Exchange (IX) bereitgestellt, im Wesentlichen ein gemeinsamer Hub, der uns mit vielen anderen Netzwerken verbindet. Wenn unsere eigene Verbindung zum IX gesunken wäre, hätte es alle Kunden gleichermaßen betroffen, aber das war hier nicht der Fall. Basierend auf dem, was wir sehen, ist es möglich, dass eine Teilmenge von Netzwerken, die die gleiche Infrastruktur am IX teilen, ein lokalisiertes Problem hatte, was erklären würde, warum nur einige Kunden ein Problem bemerkten, während andere dies nicht taten. Wir wollen transparent sein, dass dies unsere beste Arbeitstheorie ist und nicht eine bestätigte Ursache, da wir nicht die volle Transparenz über dieses bestimmte Stück Infrastruktur haben. Wir haben uns auch bei unserem Upstream-Anbieter erkundigt und sie haben bestätigt, dass alle Systeme an ihrem Ende während dieses Zeitraums als gesund erwiesen haben. Wir werden weiterhin genau beobachten, und wir werden Sie aktualisieren, wenn wir etwas weiter lernen. Bitte lassen Sie uns wissen, wenn Sie noch Probleme haben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. September 2026 um 20:35 UTCidentified

   Unser Team hat das Problem identifiziert, das zu Verzögerungen bei der DNS-Auflösung und Timeouts geführt hat. Engineering arbeitet aktiv daran, einen Fix zu implementieren, um Dienste zu beheben und wiederherzustellen. Der aktualisierte Status wird so schnell wie möglich bereitgestellt. Sie können auch mit Updates Schritt halten, indem Sie unsere Statusseite hier lesen: https://status.dnsfilter.com/

2. 17. September 2026 um 20:47 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 17. September 2026 um 21:00 UTCresolved

   Wir haben die Ursache der Latenzprobleme identifiziert, die bestimmte Kunden in der Westküste betreffen, und einen Fix implementiert. Der Verkehr ist auf ein stabiles Niveau zurückgekehrt, und der Dienst funktioniert normal. Wir werden die Region weiterhin genau beobachten, um weiterhin Stabilität zu gewährleisten. Wenn Sie weiterhin Probleme haben, wenden Sie sich bitte an unser Support-Team, um Unterstützung zu erhalten

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. September 2026 um 16:22 UTCidentified

   Wir haben die Ursache eines Problems identifiziert, das die Berichterstattung betrifft. Kunden können das DNS-Abfrageprotokoll möglicherweise nicht laden oder sehen Verzögerungen beim Anzeigen von Berichtsdaten im Dashboard. Unser Team arbeitet an einer vollständigen Lösung. Wenn Sie in der Zwischenzeit Fragen haben, kontaktieren Sie bitte unser Support-Team. Wir werden in Kürze weitere Updates bereitstellen.

2. 14. September 2026 um 16:48 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse

3. 14. September 2026 um 17:09 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 3. Juni 2026 um 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 um 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 um 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 um 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 um 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 um 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 um 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 um 16:11 UTCmonitoring

   We are continuing to monitor this issue.

3. 9. Mai 2026 um 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. April 2026 um 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. April 2026 um 12:47 UTCmonitoring

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

3. 27. April 2026 um 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. März 2026 um 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. März 2026 um 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. März 2026 um 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. Dezember 2025 um 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. Dezember 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 12:26 UTCinvestigating

   We are continuing to investigate this issue.

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

   This incident has been resolved.

1. 20. Oktober 2025 um 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. Oktober 2025 um 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. September 2025 um 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. September 2025 um 18:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29. September 2025 um 18:28 UTCmonitoring

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

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

   This incident has been resolved.

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

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

3. 14. Juli 2025 um 13:52 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 14. Juli 2025 um 17:04 UTCresolved

   This incident has been resolved.

5. 15. Juli 2025 um 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. Juni 2025 um 15:56 UTCinvestigating

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

2. 24. Juni 2025 um 16:45 UTCmonitoring

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

3. 24. Juni 2025 um 18:40 UTCresolved

   This incident has been resolved.