- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Web Application
- Regions
- us
What to do
Check whether you use Secureframe Web Application in us. 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 2h 21m it lasted.
Anything that failed between 2025-12-12 18:51 UTC and 2025-12-12 21:12 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 6
- investigating
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
The issue has been identified and we are implementing a fix.
provider
- identified
We have validated a fix for this issue, and will be deploying this fix to our Production code and all regions shortly.
provider
- resolved
This incident has been resolved.
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-b371d9a03a
Is Secureframe still down?
No, this incident was resolved 2025-12-12 21:12 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
2h 21m, from 2025-12-12 18:51 UTC to 2025-12-12 21:12 UTC, by the times Secureframe posted.
What was affected?
Secureframe named Web Application in us.
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.