Resolved -
DNS policies should now be operating normally. We apologize for any inconvenience caused by this issue and have enhanced our reporting to monitor interruptions in policy API data flow.
Jun 6, 16:12 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Jun 5, 16:30 UTC
Identified -
The team uncovered a malformed data error in our publishing API that has affected the API's ability to update devices with policy configurations. Upon removal of the malformed data, the publishing API continued normal operation and has since processed a backlog of policy updates.
Jun 5, 13:58 UTC
Update -
We are continuing to investigate this issue.
Jun 4, 16:21 UTC
Investigating -
We're currently investigating why some devices are not functioning according to custom and default DNS Protection policies.
Jun 4, 15:30 UTC