For the complete documentation index, see llms.txt. This page is also available as Markdown.

Fallback setting

Maintaining a stable connection is our top priority. To ensure reliability, we’ve built multiple layers of redundancy so that in the event of issues such as network disruptions or hardware failures, the service will automatically recover within a few minutes.

When the service is restored, the connection may temporarily switch to a different IP address, which in certain cases (such as with some proprietary trading firms) could potentially violate specific rules.

For this reason, we’ve integrated this feature that allows you to configure how the system behaves during fallback, giving you full control over the recovery process.

Settings

Fallback settings
  • Allowed Regions: Specify a list of regions where the account can be moved in case of an issue. By default, all regions will be used except New York.

  • No Fallback: Enable this option to disable fallback. The account will remain disconnected until the service is restored. This option is considered only if the account is using a dedicated IP. By default this option is disabled

Accounts vs Project Level Fallback

  • Account-Level Fallback: The feature can be applied to individual accounts, ensuring they are dynamically reassigned to operational regions during issues.

  • Project-Wide Fallback: When applied to a project, the fallback behavior is inherited by all accounts under that project, streamlining regional failover for multiple accounts.

Last updated