Steps taken to minimize 'Interruption of Service'

    Applies to:
  • Arculix
Deployment model:
  • Cloud
  • Description:

    This article will be used to inform what all steps have been taken to minimize Interruption of Service.

    • DNS is being moved to AWS Route 53 with Arculix, which is multi-region
    • We operate in multiple availability zones within an AWS region, which provides region-based redundancy
    • The Arculix/Acceptto environment will be in multiple regions – currently there would be up to a 15 minute outage if we had to manually switch regions; however, we are in the process of making any move to a different region happen almost instantaneous. We will have this multi-region, little to no downtime setup for Arculix/Acceptto by the end of the year.
    • In the case an upstream provider has an issue (for example, the one highlighted below) we are working in parallel with the previous bullet by having redundant services so any impact to one of the upstream providers could be rapidly switched to a backup vendor or another region that is not having the issue.
    • Finally, we are utilizing microservices and containers for the services, so if one service fails, it can quickly and easily be restarted if the container service does not automatically restart the container.

    If there are any queries, feel free to reach out to us at


    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.


    0 out of 0 found this helpful



    Please sign in to leave a comment.