Securly Outage History

Securly experienced degraded login performance due to Google SSO problems affecting the Pass and Flex user interfaces. Some users were unable to sign in using Google credentials during the incident, which impacted access for those features. The outage began at 1:45 PM UTC and was resolved by 4:20 PM UTC. The two affected components were Pass / User Interface and Flex / User Interface.

Status communications indicated the problem and active investigation, followed by restoration of the affected sign-in flows. The incident involved two official updates from Securly as the issue progressed, and user reports described login page failures during the degraded period. A sample report noted login difficulties observed by a user.

Securly experienced a regional disruption to dashboard access due to CloudFront CDN issues. Users in multiple regions including North America, the UK, and Canada reported intermittent visibility and UI responsiveness affecting the Home / User Interface and regional filters. The incident began for many around 9:00 PM UTC and was acknowledged by Securly at Feb 10, 2026 9:40 PM UTC with a note about CloudFront issues and regional impact.

The outage affected Securly's global filter service, where proxy detection signatures misclassified sites as Network Misuse/Proxy, causing instability across filtering components. All clusters entered CIPA Compliance mode to prevent blocking miscategorized domains while remediation progressed. The incident impacted five filter components: USEAST2, USWEST, UK, CANADA, and USEAST. The outage began at Jan 30, 2026 3:35 PM UTC and was resolved by Jan 31, 2026 12:20 AM UTC, lasting roughly 8 hours and 45 minutes.

Two official status updates were posted by Securly during the incident, documenting the investigation and remediation steps. Once the misclassification issue was addressed, the affected components returned to normal operation and general service stability was restored.

From 1:38 PM UTC to 2:47 PM UTC, Securly Filter blocked access to websites that were normally allowed, disrupting classroom activities and school workflows for students and staff. Reports from multiple locations in the United States—including Brooklyn, Ashburn, Arlington Heights, Orlando, and Middletown—described widespread over-blocking and degraded filtering performance, preventing access to typical educational resources during the period.

StatusGator detected the issue at Jan 30, 2026 1:38 PM UTC ahead of any official acknowledgment. Securly did not publish a status page update during the incident, and the outage was resolved by 2:47 PM UTC. The impact appeared broad across the United States based on user reports, but no root-cause details were provided in updates. Affected component: Securly Filter.

An AWS reliability incident caused a partial disruption across most Securly services and APIs. The outage began at 9:10 AM UTC and impacted 17 components across user interfaces and backend services (Flex / User Interface, DyKnow Classroom / User Interface, Reveal / User Interface, Pass / User Interface, Classroom / User Interface, Device Console / Classroom, Device Console / MDM, Rhithm / User Interface, Filter / USEAST2, Filter / USWEST, Filter / UK, Filter / CANADA, Aware / OnCall, Aware / User Interface, Home / User Interface, MDM / User Interface, Filter / USEAST). Users experienced partial outages and degraded performance across affected areas. The incident lasted about 1 hour 15 minutes and was resolved by 10:25 AM UTC. The provider issued 2 status updates during the incident to communicate progression and recovery, and the disruption appeared broad across Securly products and services.

The UK cluster of Securly experienced a dedicated issue affecting the Activity Log and Reporting system, causing activity data to be captured but not displayed in the user interface for Filter / UK and the related UI components. This disrupted reporting dashboards for UK users. The problem began at 12:00 PM UTC and persisted for about 24 hours and 20 minutes, with full visibility restored after maintenance completed by 12:20 PM UTC. The affected components were Filter / UK, Home / User Interface, and Aware / User Interface. The incident was localized to the UK region and spanned four status updates during its course.

In the USEast region, Securly's Filter service experienced increased errors following a recent release, resulting in degraded filtering performance for users in that region. The issue affected the Filter / USEAST component and caused intermittent issues with applying filters. A rollback of the release was initiated and normal operation was expected to resume shortly. The incident began at 7:05 PM UTC when the status page moved to a degraded state. The provider issued two status updates during this incident.

By 8:30 PM UTC, normal operation was restored as the rollback completed, with impact limited to the USEast region rather than a global outage.

An AWS outage triggered a service disruption for Securly, impacting 17 components across Classroom UI, Device Console, MDM, and regional filters (USEAST2, USWEST, UK, CANADA). Users could experience sign-in issues and intermittent access across the platform. The incident began at 12:30 PM UTC and persisted for about 9 hours and 15 minutes, with a major recovery underway by 9:45 PM UTC. The provider issued three official status updates during the event as infrastructure changes were applied.

An outage affected Securly's USEast filtering, temporarily limiting access to the Safety Console. Securly activated CIPA Compliance Mode to safeguard student browsing while diagnosing the issue, with three components shown degraded: Home / User Interface, Aware / User Interface, and Filter / USEAST. The incident began at Oct 9, 2025 6:40 PM UTC and was resolved by Oct 9, 2025 8:45 PM UTC, lasting about 2 hours and 5 minutes. The provider posted two status updates during the incident, and user reports were limited in volume with some reports originating from the US region.

An incident affecting Google SSO authentication began at 2:25 PM UTC and disrupted sign-ins for Securly users across multiple interfaces. Google SSO login failures impacted 17 components spanning Reveal, Pass, Flex, MDM, Classroom, Device Console, Rhithm, DyKnow Classroom, and regional filters (USEAST, USEAST2, USWEST, UK, CANADA). The outage hindered access to dashboards and classroom tools and lasted about 6 hours.

The provider’s status page documented three official updates: the initial alert at 2:25 PM UTC noting a Google SSO Issue and ongoing investigation, a follow-up at 2:40 PM UTC confirming continued investigation with several components degraded, and a final update at 8:25 PM UTC indicating recovery and return to normal (status moved to up).