- 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
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 1h 3m it lasted.
Anything that failed between 2023-07-07 15:01 UTC and 2023-07-07 16:04 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 4
- investigating
We are investigating this issue.
provider
- investigating
We have increased system resources to improve sync times: this should allow syncing to complete more quickly and reduce overall latency.
provider
- monitoring
We have alleviated the main cause of delays. Some nightly integration sync jobs are still completing.
provider
- resolved
All remaining daily syncs are running normally and will complete within the next 1-2 hours.
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-a868097291
Is Secureframe still down?
No, this incident was resolved 2023-07-07 16:04 UTC. For Secureframe's live state, see https://down.guide/providers/secureframe.
How long did it last?
1h 3m, from 2023-07-07 15:01 UTC to 2023-07-07 16:04 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.