DNSFilter Status

Resolved: This incident has now been resolved.

Monitoring: We have identified the cause of the issue where traffic intended for our service via DNS2 is unexpectedly being routed to our DNS1 servers, which began on March 30th, 2025, at 18:10 UTC.

We are now monitoring the implementation of the solution. While investigating the initial misrouting, we currently observe no increase in latency.

Further updates on the resolution will be provided as they become available. Thank you for your patience.

Investigating: We understand the recent DNS resolution disruptions may have caused inconvenience, and we sincerely apologize for any impact this has had on your operations. Please know maintaining a reliable service is a top priority for us, and we are actively working to resolve these issues as quickly as possible.

On March 30th, 2025, starting at 18:10 UTC, our systems detected traffic intended for our service via DNS2 was unexpectedly being routed to our servers handling traffic over DNS1.

While we are currently investigating the cause of this misrouting, we want to assure you that we are not observing any increase in latency at this time. Our team is engaged to examine this issue and implement a solution. We recognize the importance of keeping you informed and will provide further updates as soon as they are available.

Thank you for your patience and understanding as we work diligently to restore optimal service.

Resolved: This incident has now been resolved.

Monitoring: We have identified the cause of the issue where traffic intended for our service via DNS2 is unexpectedly being routed to our DNS1 servers, which began on March 30th, 2025, at 18:10 UTC.

We are now monitoring the implementation of the solution. While investigating the initial misrouting, we currently observe no increase in latency.

Further updates on the resolution will be provided as they become available. Thank you for your patience.

Investigating: We understand the recent DNS resolution disruptions may have caused inconvenience, and we sincerely apologize for any impact this has had on your operations. Please know maintaining a reliable service is a top priority for us, and we are actively working to resolve these issues as quickly as possible.

On March 30th, 2025, starting at 18:10 UTC, our systems detected traffic intended for our service via DNS2 was unexpectedly being routed to our servers handling traffic over DNS1.

While we are currently investigating the cause of this misrouting, we want to assure you that we are not observing any increase in latency at this time. Our team is engaged to examine this issue and implement a solution. We recognize the importance of keeping you informed and will provide further updates as soon as they are available.

Thank you for your patience and understanding as we work diligently to restore optimal service.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are now monitoring the results. Thank you for your understanding.

Investigating: Date of Incident: Mar 25, 2025 Time: 2PM UTC Affected Systems/Services: MFA Incident Priority Level: Medium Description: We are currently investigating reports of users being prompted to re-setup their Multi-Factor Authentication (MFA) in order to access the dashboard. This is not intended behavior, and we understand the inconvenience it causes. Impact: Users may be unable to access the dashboard without re-setting up their MFA. This issue affects users utilizing MFA for login. There are no impacts to security policies. Current Status: Our engineering team is actively investigating the root cause of this unexpected MFA re-setup request. We are working to identify and implement a solution as quickly as possible. We are monitoring system logs and authentication services.