Securly Outage History

Securly Filter experienced an issue where some traffic, specifically Azure SmartPAC user traffic, was incorrectly being logged and blocked under the Default Policy instead of the appropriate filtering rules. The incident affected the Safety Console component and lasted 3.4 hours. The team investigated the root cause and resolved the filtering policy issue.

Securly Filter experienced stability issues affecting the Safety Console for 40 minutes due to a recent release impacting the UK cluster. The incident was identified as affecting the UK cluster specifically, with the team actively working on a solution. The service was restored after the 40-minute duration.

Securly experienced a major outage affecting their Rhithm component that lasted 20.9 hours. The service was completely inaccessible during this period. The incident was acknowledged and investigated by the team, though no resolution details were provided in the available updates.

Securly's browser extension experienced a failure in YouTube keyword scanning due to a recent change in YouTube's Search API that introduced payload compression the extension couldn't process. The issue affected the Safety Console component and prevented proper content monitoring on YouTube through the browser extension. The engineering team investigated and worked on a fix for this high-priority issue over a 68.5-hour period.