Skip to main content
Secureframe

Secureframe - issues with updating Cloud Sync results

Degraded Lasted 3h · started · Secureframe's page

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 it lasted.

    Anything that failed between 2023-01-17 16:03 UTC and 2023-01-17 19:03 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 6

  1. identified

    Some customers may experience 'Sync Failed' messages in the application as well as test refreshing due to an outage in our backend storage system. We have identified a cause, and have taken steps to resolve this issue and are still actively investigating.

    provider

  2. identified

    We are continuing to work on this issue - we are testing resolutions at this time.

    provider

  3. identified

    We are continuing to work on this issue; AWS syncing should now function correctly, other cloud platforms are nearing resolution.

    provider

  4. identified

    GCP syncing should now be working normally,

    provider

  5. identified

    This incident has been resolved.

    provider

  6. 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-a256b92fb9

Is Secureframe still down?

No, this incident was resolved 2023-01-17 19:03 UTC. For Secureframe's live state, see https://down.guide/secureframe.

How long did it last?

3h, from 2023-01-17 16:03 UTC to 2023-01-17 19:03 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.