- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Web Application, API
- Down Index
- 33of 100
What to do
Check whether you use Secureframe Web Application, API. 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 50m it lasted.
Anything that failed between 2022-11-30 23:15 UTC and 2022-12-01 00: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
We have received reports of customers not being able to load part or all of Secureframe. We are investigating. This is due to an upstream provider outage. We are monitoring those systems.
provider
- monitoring
This issue has been resolved by the upstream provider, we will continue to monitor the application's performance. Application performance should be normal for all users at this time.
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-9fce33a749
Is Secureframe still down?
No, this incident was resolved 2022-12-01 00:05 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
50m, from 2022-11-30 23:15 UTC to 2022-12-01 00:05 UTC, by the times Secureframe posted.
What was affected?
Secureframe named Web Application, API.
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.