- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Application
- Down Index
- 18of 100
What to do
Check whether you use Secureframe Web Application. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 25m it lasted.
Anything that failed between 2026-04-01 16:11 UTC and 2026-04-01 16:36 UTC may need a replay.Subscribe to Secureframe's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=secureframe works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Secureframe 3
- identified
We have identified an issue where Cloud Syncs failed overnight, and may have incorrectly updated Cloud Test statuses.
provider
- identified
We have started remediation to resync these connections across the plaform.
provider
- resolved
This incident has been resolved, and tests should now show the correct values.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f9f77d9c7f
Is Secureframe still down?
No, this incident was resolved 2026-04-01 16:36 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
25m, from 2026-04-01 16:11 UTC to 2026-04-01 16:36 UTC, by the times Secureframe posted.
What was affected?
Secureframe named Web Application.
What caused it?
Secureframe hasn't published a root cause. If it does, it shows here.
Where does this come from?
Secureframe's official status page, https://status.secureframe.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.