- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Application
- Down Index
- 20of 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 47m it lasted.
Anything that failed between 2023-04-03 19:45 UTC and 2023-04-03 20:33 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 2
- investigating
Some customers may experience delays when attempting to manually sync integrations, or refresh tests in the Secureframe app. We are investigating the incident.
provider
- resolved
We temporarily increased infrastructure resources in order to reduce a backlog of background jobs that were preventing integration syncing and test refreshes. This incident is resolved, and we are continuing to investigate root causes and monitoring.
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-f52fbb68dd
Is Secureframe still down?
No, this incident was resolved 2023-04-03 20:33 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
47m, from 2023-04-03 19:45 UTC to 2023-04-03 20:33 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.