- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Secureframe Agent
What to do
Check whether you use Secureframe Secureframe Agent. 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 1h 17m it lasted.
Anything that failed between 2024-04-10 18:48 UTC and 2024-04-10 20:05 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
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
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-96af1f84da
Is Secureframe still down?
No, this incident was resolved 2024-04-10 20:05 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
1h 17m, from 2024-04-10 18:48 UTC to 2024-04-10 20:05 UTC, by the times Secureframe posted.
What was affected?
Secureframe named Secureframe Agent.
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.