Securly incident
Some traffic being logged/blocked as Default Policy
Securly experienced a minor incident on May 19, 2026 affecting Filter and Filter (USEAST) and 1 more component, lasting 22h 31m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 19, 2026, 11:04 AM UTC
We have detected an issue with Securly Filter related to some traffic being logged/blocked as Default Policy. Our team is currently investigating the root cause to ensure a swift resolution. We apologize for any inconvenience and will provide updates as soon as possible. If you are experiencing this issue, please check back soon for an update.
- identified May 19, 2026, 02:02 PM UTC
We have detected an issue with Securly Filter related to Azure SmartPAC user traffic being logged/blocked as Default Policy. Our team is currently investigating the root cause to ensure a swift resolution. We apologize for any inconvenience and will provide updates as soon as possible. If you are experiencing this issue, please check back soon for an update.
- monitoring May 19, 2026, 02:24 PM UTC
We have implemented a fix for the issue with Securly Filter related to Azure SmartPAC user traffic being logged/blocked as Default Policy. Functionality should now be restored for most users, and we are closely monitoring the system to ensure stability.
- monitoring May 19, 2026, 03:21 PM UTC
We have implemented a fix for the issue with Securly Filter related to Azure SmartPAC user traffic being logged/blocked as Default Policy. Functionality should now be restored for most users, and we are closely monitoring the system to ensure stability.