Securly Status

May 27, 2026 10:19AM EDT Investigating - Some Pass clients are having issues seeing all passes on their dashboard. We are aware of the issue and investigating the root cause to create a fix. May 27, 2026 10:50AM EDT Resolved - We have identified the issue and released a fix to the Pass Dashboard. Please reach out to support if you continue to experience issues with the dashboard.

May 19, 2026 7:04AM EDT Investigating - 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. May 19, 2026 10:02AM EDT Identified - 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. May 19, 2026 10:24AM EDT Monitoring - 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. May 19, 2026 11:21AM EDT Monitoring - 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. May 20, 2026 5:31AM EDT Resolved - The issue with Securly Filter regarding Securly Filter related to Azure SmartPAC user traffic being logged/blocked as Default Policy. Normal functionality is now restored for all users. We apologize for any inconvenience caused and thank you for your patience during this process. If you have any further concerns, please don’t hesitate to contact our support team.

April 29, 2026 5:33AM EDT Investigating - We have detected an issue with Securly Filter related to stability issues. 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 our SRE system for updates. April 29, 2026 5:46AM EDT Identified - We have identified an issue with Securly Filter where a recent release is affecting our UK cluster. Our team is actively working on a solution to restore full functionality as quickly as possible. We appreciate your patience and will keep you updated on our progress. April 29, 2026 6:11AM EDT Monitoring - We have implemented a fix for the issue with Securly Filter related to UK cluster stability. Functionality should now be restored for most users, and we are closely monitoring the system to ensure stability. If you continue to experience issues, please contact our support team for further assistance. We apologize for the inconvenience and thank you for your patience. April 29, 2026 8:21AM EDT Resolved - The issue with Securly Filter regarding UK cluster stability has been fully resolved. Normal functionality is now restored for all users. We apologize for any inconvenience caused and thank you for your patience during this process. If you have any further concerns, please don’t hesitate to contact our support team.

March 26, 2026 1:50PM EDT Investigating - We are currently experiencing a Rhithm outage. The team is investigating. March 27, 2026 10:42AM EDT Resolved - The issue affecting Rhithm has been resolved and the service is back up. Thank you for your patience.

March 9, 2026 4:04PM EDT Investigating - We are aware of an issue affecting YouTube keyword scanning for users on the Securly browser extension. A recent change to the YouTube Search API introduced payload compression that the extension is currently unable to process, causing keyword scanning on YouTube to fail. What is affected: YouTube keyword scanning via the browser extension. Current status: Our engineering team is actively investigating and evaluating a fix. This is being treated as our highest priority and we will provide an update as soon as we have more information on timing and resolution. March 12, 2026 12:28PM EDT Resolved - Our development team has released a fix for this issue with an updated extension version of 3.0.36. The extension update may take up to 24 for hours to reach all devices. If you continue to experience issues with YouTube keyword logging on extension devices after the updated extension has been applied, please reach out to our support team.

February 19, 2026 8:43AM EST Investigating - Securly Pass and Flex are facing issues with Google SSO. We are actively investigating the solution and will provide an update once it is resolved February 19, 2026 11:20AM EST Resolved - We have identified and released a fix to resolve the issue with Google SSO in Pass and Flex. Please verify that you can now sign in. If you run into any further issues with Google SSO, please reach out to our support team

February 10, 2026 4:31PM EST Investigating - We have detected issues with Amazon's Content Delivery Network (CDN) CloudFront. Access to Securly dashboards may be affected on a regional basis. We will post updates as we learn more. February 10, 2026 5:42PM EST Resolved - We have been notified that the AWS issues with CloudFront Distribution has been resolved and all Securly services have resumed normal operations.

February 2, 2026 12:16PM EST Identified - Ignore February 2, 2026 12:19PM EST Identified - Ignore February 2, 2026 12:19PM EST Resolved - Test complete.

January 30, 2026 7:56AM EST Investigating - We are entering CIPA compliance mode to shed load from our services. CIPA compliance mode allows us to filter with a global CIPA policy while we investigate the issues. January 30, 2026 10:34AM EST Identified - During our investigation, we found that our proxy detection signatures acted abnormally and categorized a number of sites as Network Misuse/Proxy. In addition to the current AWS health issues this caused additional load on our infrastructure resulting in instability. All clusters are in CIPA Compliance mode which will ensure the miscategorized domains will no longer be blocked while we remediate the issue. We will provide regular updates on Securly’s Status Page https://status.securly.com January 30, 2026 12:23PM EST Identified - We are restoring nightly database backups on a cluster-by-cluster basis to correct the miscategorized sites. After each restore, we run our standard QA test cases and perform manual validation to confirm the fix was successful. Once we confirm the restore executed successfully, we will return that cluster back to normal operating mode. We are 40% complete as of writing this. We will continue to share regular updates on Securly’s Status Page https://status.securly.com January 30, 2026 2:44PM EST Identified - While restoring clusters to normal operating mode, during testing and validation, we detected additional anomalies in the categorization system. To prevent further miscategorization of sites, we reverted systems to CIPA compliance mode. We have identified and addressed the source of the additional miscategorization and will continue to recover from CIPA mode. January 30, 2026 7:15PM EST Resolved - All Securly clusters are currently operating normally with no additional categorization anomalies detected at this time. Securly will continue to closely monitor and provide updates through the weekend, as appropriate. If you continue to see any anomalies please report those through support. We will follow-up with Securly Filter partners via email over the coming days on root cause and additional information once we complete our investigation.

January 30, 2026 4:06AM EST Investigating - AWS reliability issues are affecting most Securly services and APIs resulting in partial service disruption. The team are investigating. January 30, 2026 5:24AM EST Monitoring - Systems are stable and we are resuming normal operations. January 30, 2026 7:57AM EST Resolved - The AWS issues have been resolved in the UK. Closing this incident and opening a global incident.