Istoricul incidentelor Webshrinker

1. 28 septembrie 2026 la 12:51 UTCidentified

   Echipa noastră de inginerie a identificat o problemă care cauzează tabloul de bord să nu reflecte modificările corect în cadrul UI și este în prezent de lucru pentru a implementa un fix pentru a remedia problema. Schimbările sunt active şi funcţionează conform aşteptărilor. Există în prezent o întârziere de până la 30 de minute înainte de a apărea în tabloul de bord, astfel încât ceea ce vedeți nu poate reflecta cele mai recente actualizări încă. Vom oferi statutul actualizat cât mai curând posibil odată ce o fix a fost implementat.

2. 28 septembrie 2026 la 14:35 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

3. 28 septembrie 2026 la 15:29 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 28 septembrie 2026 la 15:45 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 22 septembrie 2026 la 12:14 UTCinvestigating

   Echipa noastră de ingineri investighează în prezent o problemă care face ca rezoluția DNS să fie intermitentă în întreaga regiune a Regatului Unit și lucrează în prezent cu partenerii noștri pentru a rezolva situația.

2. 22 septembrie 2026 la 12:26 UTCmonitoring

   Rezoluţia a revenit şi funcţionează; ingineria este monitorizarea.

3. 22 septembrie 2026 la 14:26 UTCresolved

   Conectivitatea noastră este asigurată printr-un Internet Exchange (IX), în esență un hub comun care ne conectează cu multe alte rețele. Dacă propria noastră legătură cu IX ar fi căzut, ar fi afectat toţi clienţii în mod egal, dar nu aşa era cazul aici. Bazat pe ceea ce vedem, este posibil ca un subset de rețele care partajează aceeași infrastructură la IX să fi experimentat o problemă localizată, ceea ce ar explica de ce doar unii clienți au observat o problemă în timp ce alții nu. Dorim să fim transparenţi că aceasta este cea mai bună teorie a noastră de lucru mai degrabă decât o cauză fundamentală confirmată, deoarece nu avem vizibilitate deplină în acea bucată specifică de infrastructură. Am verificat, de asemenea, cu furnizorul nostru din amonte, și au confirmat că toate sistemele de la sfârșitul lor a arătat ca sănătos pe parcursul acestei perioade. Continuăm să monitorizăm îndeaproape şi te vom actualiza dacă vom afla ceva mai mult. Te rog să ne spui dacă mai ai probleme.

Traducere automată din actualizarea oficială a incidentului.

1. 17 septembrie 2026 la 20:35 UTCidentified

   Echipa noastră a identificat problema care a cauzat latență rezoluție DNS și timeouts. Ingineria lucrează în mod activ la implementarea unui fix pentru remedierea și restabilirea serviciilor. Starea actualizată va fi furnizată cât mai curând posibil. De asemenea, puteți ține pasul cu actualizările prin revizuirea paginii noastre de stare aici: https://status.dnsfilter.com/

2. 17 septembrie 2026 la 20:47 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 17 septembrie 2026 la 21:00 UTCresolved

   Am identificat cauza principală a problemelor de latenţă care afectează anumiţi clienţi din regiunea Coasta de Vest şi am pus în aplicare o soluţie. Traficul a revenit la niveluri stabile, iar serviciul funcționează normal. Vom continua să monitorizăm îndeaproape regiunea pentru a asigura stabilitatea continuă. Dacă continuați să experimentați probleme, vă rugăm să contactați echipa noastră de sprijin pentru asistență

Traducere automată din actualizarea oficială a incidentului.

1. 14 septembrie 2026 la 16:22 UTCidentified

   Am identificat cauza unei probleme care afectează raportarea. Clienții pot fi în imposibilitatea de a încărca jurnalul de întrebări DNS sau de a vedea întârzierile în vizualizarea datelor de raport în tabloul de bord. Echipa noastră lucrează pentru o rezoluţie completă. Dacă aveți întrebări între timp, vă rugăm să contactați echipa noastră de sprijin. Vom furniza în curând actualizări suplimentare.

2. 14 septembrie 2026 la 16:48 UTCmonitoring

   A fost implementat un fix şi monitorizăm rezultatele

3. 14 septembrie 2026 la 17:09 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

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

   We are continuing to monitor this issue.

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

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

3. 27 aprilie 2026 la 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 martie 2026 la 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 martie 2026 la 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 martie 2026 la 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 decembrie 2025 la 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 decembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 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 noiembrie 2025 la 12:26 UTCinvestigating

   We are continuing to investigate this issue.

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

   This incident has been resolved.

1. 20 octombrie 2025 la 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 octombrie 2025 la 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 septembrie 2025 la 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 septembrie 2025 la 18:27 UTCinvestigating

   We are continuing to investigate this issue.

3. 29 septembrie 2025 la 18:28 UTCmonitoring

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

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

   This incident has been resolved.

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

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

3. 14 iulie 2025 la 13:52 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 14 iulie 2025 la 17:04 UTCresolved

   This incident has been resolved.

5. 15 iulie 2025 la 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 iunie 2025 la 15:56 UTCinvestigating

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

2. 24 iunie 2025 la 16:45 UTCmonitoring

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

3. 24 iunie 2025 la 18:40 UTCresolved

   This incident has been resolved.