Skip to main content
down.guideby Sazabi
Menu
Secureframe

Incident

Company Tests/Test Library May Show Incomplete Results

Degraded Lasted 4h 39m · started · Secureframe's page

DWN-bcf0387327SecureframeResolved

Level
confirmed
Worst impact
Degraded
Components
Web Application
Down Index
24of 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 4h 39m it lasted.

    Anything that failed between 2025-02-06 15:41 UTC and 2025-02-06 20:20 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 7

  1. identified

    Some data in Company Test and Test Libraries may not be showing in the application. We have a mitigation strategy in place and are updating data now.

    provider

  2. identified

    We are continuing to work on this issue.

    provider

  3. monitoring

    We are currently remediating this issue, and users should start seeing more tests data, and can manually refresh tests in the app as needed.

    provider

  4. monitoring

    Remediation is still in progress. Overall the application is operational.

    provider

  5. monitoring

    Most data has been restored at this time, and we estimate full restoration within the next 2 hours.

    provider

  6. monitoring

    The remediation is nearing completion. This status will be updated when complete.

    provider

  7. 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-bcf0387327

Is Secureframe still down?

No, this incident was resolved 2025-02-06 20:20 UTC. For Secureframe's live state, see https://down.guide/providers/secureframe.

How long did it last?

4h 39m, from 2025-02-06 15:41 UTC to 2025-02-06 20:20 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.

Sources

Feed