- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Application
- Regions
- eu, us
- Down Index
- 25of 100
What to do
Check whether you use Secureframe Web Application in eu, us. 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 1h 1m it lasted.
Anything that failed between 2022-08-23 23:25 UTC and 2022-08-24 00:26 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
Our hosting provider is having a DNS outage. More information can be found here https://status.heroku.com/incidents/2453
provider
- identified
We are continuing the monitor the situation at our hosting provider. It's a widespread issue impacting their customers in the US and Europe. They are currently working on a solution https://status.heroku.com/
provider
- resolved
We have found a workaround to the hosting providers ongoing issue.
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-8a62102f34
Is Secureframe still down?
No, this incident was resolved 2022-08-24 00:26 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
1h 1m, from 2022-08-23 23:25 UTC to 2022-08-24 00:26 UTC, by the times Secureframe posted.
What was affected?
Secureframe named Web Application in eu, us.
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.