Secureframe Outage History
9 incidents recorded over the last 365 days, 9 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 Secureframe Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 10, 2026 | Elevated errors with third party vendorThe third-party service has recovered and all affected services are fully operational. We've confirmed normal performance. Thank you for your patience. | 1h 32m | Resolved |
| Jun 9, 2026 | Secureframe Agent devices missing from inventoryThis incident has been resolved. | 7h 32m | Resolved |
| May 27, 2026 | Sign in issues with "Sign in with Microsoft"This incident has been resolved. | 32 min | Resolved |
| Apr 1, 2026 | Cloud Sync Failures - Secureframe PlatformThis incident has been resolved, and tests should now show the correct values. | 25 min | Resolved |
| Feb 23, 2026 | Secureframe Agent - UK - syncs are not workingThis incident has been resolved. | 3h 15m | Resolved |
| Jan 20, 2026 | Issues with Google Workspace connectionsThis incident has been resolved. | 7h 1m | Resolved |
| Dec 12, 2025 | Personnel Page Crashing for US/UK usersThis incident has been resolved. | 2h 21m | Resolved |
| Dec 5, 2025 | Increased error rates with loginThis incident has been resolved. | 13 min | Resolved |
| Nov 18, 2025 | Secureframe US and UK appplications unavailableCloudflare has implemented a fix to their service. The Secureframe app is functioning normally at this time. | 2h 33m | 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 Secureframe 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 Secureframe 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 Secureframe 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 Secureframe outage in this window ran 7h 32m, against a mean recovery of 2h 49m. If you depend on Secureframe 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.