- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Application
- Down Index
- 23of 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 3h 3m it lasted.
Anything that failed between 2023-06-05 19:55 UTC and 2023-06-05 22:58 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 5
- investigating
We are investigating an increased number of incorrect findings in our AWS test findings, specifically WAFV2: GetLoggingConfiguration.
provider
- investigating
We are continuing to investigate this error.
provider
- investigating
This error can show across all AWS tests in some cases. We are continuing to investigate a solution.
provider
- investigating
We are continuing to investigate this issue. We have taken remediation steps to reduce and/or resolve test results that incorrectly show failed results, and as AWS accounts sync, these cosmetic issues should resolve themselves.
provider
- resolved
We have resolved the underlying issue and all systems are operating normally. There may be some lingering errors in test results that will be resolved as our AWS syncing runs.
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-05ee83514b
Is Secureframe still down?
No, this incident was resolved 2023-06-05 22:58 UTC. For Secureframe's live state, see https://down.guide/secureframe.
How long did it last?
3h 3m, from 2023-06-05 19:55 UTC to 2023-06-05 22:58 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.