- Level
- confirmed
- Worst impact
- Degraded
- Components
- Secureframe Agent
- Down Index
- 26of 100
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 20h 12m it lasted.
Anything that failed between 2022-12-15 22:39 UTC and 2022-12-16 18:50 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. This only affects the generation of new agent packages.
provider
- identified
We have deployed a fix for installing agents. Existing agent packages did not have any issues with syncing or installation.
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-1035eeb52b
Is Secureframe still down?
No, this incident was resolved 2022-12-16 18:50 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
20h 12m, from 2022-12-15 22:39 UTC to 2022-12-16 18:50 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.