Securly outage history

Users attempting to sign in to Pass or Flex encountered redirects to the Securly sign-in page instead of entering the apps when launching from Clever or ClassLink portals, or from saved login links. The disruption began at 3:35 PM UTC and affected Pass and Flex user interfaces across the Securly product suite. While most users could still sign in by selecting a sign-in method on the Securly page, the flow was confusing and blocked direct access for some.

Over the next several hours, the team rolled out fixes. By 7:50 PM UTC the Clever portal sign-in flow had been restored and a fix for saved or bookmarked Pass login links was released. ClassLink sign-in remained affected for some users as work continued. If affected, users could sign in directly at pass.securly.com or flex.securly.com as a workaround.

By 10:45 PM UTC the Pass and Flex sign-in paths returned to normal and the UI components were reported up. Access via the direct application URLs was functioning again, and remaining issues with ClassLink had been addressed as updates progressed. In practice, most users could sign in normally, while those relying on ClassLink were advised to retry or use direct Sign-in URLs.

Securly’s Classroom user interface experienced a presence display issue, causing students to appear offline in active sessions even when they were online. The incident began at 7:30 PM UTC and affected live classrooms for roughly 21 hours until 4:35 PM UTC. Securly’s engineering team is researching the root cause and will provide updates as they learn more. The Classroom / User Interface component moved from its normal state to a degraded status during the outage and returned to normal after the issue was resolved.

Securly's Classroom UI experienced a partial outage, with some users unable to sign in and teachers seeing all available classes instead of only their own. The problem began at 12:40 PM UTC and was resolved by 1:55 PM UTC after about an hour and 15 minutes. During the incident, the Classroom / User Interface component was listed as down, affecting access and class visibility within the Classroom experience. Securly's status page indicated the team was actively investigating and would post updates as more information became available, and the service returned to normal once the issue was resolved at 1:55 PM UTC. The impact appeared limited to the Classroom UI, with no broader impact reported for other Securly services.

Users of Securly experienced CAPTCHA or 'unusual activity' verification prompts when using Google Classroom through the Classroom / User Interface. The prompts disrupted access to classroom content for some accounts, but Securly notes this is a Google-side issue and not caused by Securly. Districts nationwide were reporting the same prompts as Google works to settle Google Classroom testing activity.

Impact timeline: The issue began at 6:35 PM UTC and was resolved by 7:30 PM UTC. The Classroom / User Interface component moved from up to warn and back to up, with Google indicating that no action was needed on Securly's end and that the issue should settle as Google's testing activity concludes.

Impact began around 6:50 PM UTC when Securly entered a degraded state due to a processing issue that caused a temporary delay in some activity and flagged-event reporting. The affected components were Aware / OnCall and the Filter layers for USWEST, USEAST2, and USEAST, which led to slower activity updates and delayed flagged events for users. The engineering team identified the root cause and began reprocessing the affected data, with updates provided as recovery progressed.

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.