54 Webshrinker incidents · 2023년 10월 — official updates, affected components, duration and resolution details.
우리의 엔지니어링 팀은 UI 내에서 올바르게 반영하지 않는 대시보드를 발생시키는 이슈를 식별하고 현재 문제를 재조립하기 위해 노력하고 있습니다. 변화는 예상대로 활동하고 일합니다. 현재 대시보드에 표시하기 전에 최대 30 분의 지연이 있으므로 최신 업데이트를 반영하지 않을 수 있습니다. 수정이 완료되면 업데이트된 상태를 즉시 제공합니다.
이 문제를 해결하기 위해 계속 노력하고 있습니다.
수정이 구현되어 결과를 모니터링하고 있습니다.
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
우리의 엔지니어링 팀은 현재 영국 지역의 Intermittent로 DNS 해상도를 유발하는 문제를 조사하고 현재 우리의 파트너와 협력하여 상황을 해결합니다.
해결책은 안으로 뒤이고 일; 기술설계는 감시입니다.
우리의 연결은 Internet Exchange (IX)를 통해 제공되며, 다른 많은 네트워크와 연결되는 공유 허브입니다. IX에 대한 우리의 자신의 연결이 내려 갔다면, 그것은 모든 고객이 똑같게 영향을 받지 못했지만, 여기에는 그렇지 않았습니다. IX에서 동일한 인프라를 공유하는 네트워크의 하위 세트가 현지화 된 문제를 경험할 수 있다는 것을 알고있는 IX의 기반을 통해 다른 사람들이 문제가 발견 된 이유 만 설명 할 수 있습니다. 우리는 우리가 인프라의 특정 조각에 전체 가시성을 가지고 있지 않기 때문에, 확인 된 루트 원인보다 우리의 가장 좋은 실무 이론이다. 우리는 또한 우리의 상류 공급자로 검사하고, 그들은 그들의 끝에 모든 체계가 이 기간 내내 건강하게 보여주었다는 것을 확인했습니다. 우리는 밀접하게 감시하는 것을 계속하고, 우리는 당신을 더 배우는 경우에 새롭게 할 것입니다. 아직 문제가 발생하면 알려주세요.
공식 인시던트 업데이트를 자동 번역했습니다.
우리의 팀은 DNS 해상도 대기 시간 및 타임 아웃 발생 문제가 확인했습니다. 공학은 remediate 및 복원 서비스에 대한 수정을 시행하기 위해 적극적으로 노력하고 있습니다. 업데이트 된 상태는 가능한 한 빨리 제공됩니다. 현재 상태 페이지를 검토하여 업데이트 할 수도 있습니다. https://status.dnsfilter.com/
수정이 구현되어 결과를 모니터링하고 있습니다.
우리는 West Coast 지역의 특정 고객에게 영향을 미치는 지연 문제의 뿌리 원인을 확인하고 수정을 구현했습니다. 교통은 안정적인 수준으로 돌아 왔습니다. 서비스는 일반적으로 작동합니다. 우리는 지속적으로 안정성을 보장하기 위해 지역을 밀접하게 감시할 것입니다. 문제가 계속되면 지원 팀에 문의하시기 바랍니다
공식 인시던트 업데이트를 자동 번역했습니다.
우리는보고에 영향을 미치는 문제의 원인을 발견했습니다. 고객은 DNS Query Log를로드하거나 대쉬보드에서 보고서 데이터를 볼 때 지연을 볼 수 없습니다. 우리의 팀은 가득 차있는 해결책으로 일하고 있습니다. 그동안 궁금한 점이 있으시면 지원팀에 문의하십시오. 우리는 곧 추가 업데이트를 제공 할 것입니다.
수정이 구현되어 결과를 모니터링하고 있습니다
이 사건은 해결되었습니다.
공식 인시던트 업데이트를 자동 번역했습니다.
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.
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.
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.
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.
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.
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.
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.
We are continuing to monitor this issue.
This incident has been resolved. Our cloud partner has resolved the issue impacting reporting performance. Functionality has now returned to normal operation.
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.
A fix has been implemented and we are monitoring the results.
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.
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.
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.
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.
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.
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.
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.
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.
We are continuing to investigate this issue.
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.
This incident has been resolved.
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.
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.
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.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
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.
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.
This incident has been resolved.
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
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.
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.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
**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.
We are currently investigating an issue in the DNSFilter UI that is preventing manual customers from seeing Roaming Client.
A fix has been implemented and we are continuing to monitor the results.
This incident has been resolved.
