Secureframe had 8 outages in the last 2 years totaling 23h 55m of downtime — averaging 0.3 incidents per month.
There were 8 Secureframe outages since November 18, 2025 totaling 23h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've identified an issue where some devices managed by the Secureframe Agent dropped out of asset inventory, which is causing related tests to fail.
This incident has been resolved.
We are aware of issues with using the "Sign in with Microsoft" login to the Secureframe application. We have identified a cause and we are starting mitigation
The issue is identified, and we are also seeing Microsoft Intune syncs failing due to a similar issue. Both fixes are forthcoming shortly.
Azure Devops syncs are similarly affected, with the same fix planned.
A fix has been implemented and we are monitoring.
This incident has been resolved.
We have identified an issue where Cloud Syncs failed overnight, and may have incorrectly updated Cloud Test statuses.
We have started remediation to resync these connections across the plaform.
This incident has been resolved, and tests should now show the correct values.
We have identified the issue and are working on a remediation now.
We are continuing to work on the fix for this issue.
We are continuing to work on the fix for this issue.
We are continuing to work on the fix for this issue.
This incident has been resolved.
We have identified an issue with Secureframe integrations being disconnected from Google Workspaces, this issue has been corrected and we will reconnect any disconnected integrations affected.
We are deploying a fix for this shortly - this fix will automatically reconnect these disconnected integrations.
A fix has been implemented and is rolling out to all affected customers.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and we are implementing a fix.
We have validated a fix for this issue, and will be deploying this fix to our Production code and all regions shortly.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.