Secureframe had 14 outages in the last 2 years totaling 35h 10m of downtime — averaging 0.6 incidents per month.
There were 14 Secureframe outages since May 24, 2024 totaling 35h 10m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
Some data in Company Test and Test Libraries may not be showing in the application. We have a mitigation strategy in place and are updating data now.
We are continuing to work on this issue.
We are currently remediating this issue, and users should start seeing more tests data, and can manually refresh tests in the app as needed.
Remediation is still in progress. Overall the application is operational.
Most data has been restored at this time, and we estimate full restoration within the next 2 hours.
The remediation is nearing completion. This status will be updated when complete.
This incident has been resolved.
We are currently investigating this issue
This incident has been resolved.
We are currently investigating this issue. Other parts of the application are functioning normally.
We are investigating a possible remediation to this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have had reports of integration connections not showing up in the UI. The engineering team has identified the issue and is working on a fix.
This incident has been resolved.
We are currently investigating this error.
The issue has been identified and we are working on a resolution.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue
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.
The issue has been identified and we are working on a resolution.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are deploying a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved