Securly Outage History
5 incidents recorded over the last 365 days, 5 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Securly Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 2, 2026 | Pass and Flex sign-in issues following SSO updatePass and Flex sign-in has moved to the Securly SSO used across the Securly product suite. Since the switch this morning, some staff and students launching Pass or Flex from the Clever or ClassLink portals, or from a… | 264h 5m | Resolved |
| Sep 22, 2026 | Classroom: Student Online Status Display IssueWe're investigating reports of students appearing offline in Classroom sessions when they are actively online. Our engineering team is researching the root cause. We'll send an update as we learn more. | 21h 3m | Resolved |
| Sep 22, 2026 | Classroom: Login & Class Visibility IssueWe're aware of an issue affecting Classroom: some users are unable to access Classroom, and some teachers are seeing all available classes instead of only their own. Our team is actively investigating. We'll update this… | 1h 17m | Resolved |
| Sep 17, 2026 | Google CAPTCHA BlockingWe're aware that Google Classroom is currently throwing CAPTCHA / "unusual activity" verification prompts for some users. This is happening on Google's side, not caused by Securly, and other districts nationwide are… | 56 min | Resolved |
| Aug 28, 2026 | Delayed activity and flagged-event reportingA processing issue caused a temporary delay in some activity and flagged-event reporting. We've identified the cause and are reprocessing the affected data. | 3h 23m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Securly incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Securly Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Securly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Securly outage in this window ran 11d, against a mean recovery of 2d 10h. If you depend on Securly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.