- Level
- confirmed
- Worst impact
- Major outage
- Components
- Secureframe Agent
- Down Index
- 48of 100
What to do
Check whether you use Secureframe Secureframe Agent. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 20h 22m it lasted.
Anything that failed between 2024-04-04 21:20 UTC and 2024-04-05 17:42 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
- investigating
The Secureframe Agent is not connecting to internal services at this time. This renders Secureframe Agent unable to operate and/or report. We are working on remediation strategies at this time.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved. We are working on updating the Secureframe Agent to be less susceptible to service interruptions of this nature.
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-321c73fe16
Is Secureframe still down?
No, this incident was resolved 2024-04-05 17:42 UTC. For Secureframe's live state, see https://down.guide/providers/secureframe.
How long did it last?
20h 22m, from 2024-04-04 21:20 UTC to 2024-04-05 17:42 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.