Remote Networks

Remote networks are the logical containers that group Resources together. Resources defined within a Remote network are assumed to be accessible from any deployed Connector(s) within the same logical Remote network. When planning a Twingate deployment, a Remote network will approximately correspond to a network you are providing remote access to.

At least one Connector must be configured as part of a Remote network. Connectors are deployed behind the firewall and provide access into a Remote networkWithout a Connector deployed and running, Resources are inaccessible to Twingate end users.

We recommend running at least two Connectors in every Remote network that you configure in Twingate. There are two primary reasons to do this:

  • Load balancing and failover. Load balancing is performed automatically as the number of Connectors deployed within a Remote network is changed. In addition, if any one Connector fails, additional Connectors will be available for redundancy. You can deploy as many Connectors within a Remote network as required for your needs.
  • Scalability. As your needs grow, it may be necessary to add additional Connectors to forward additional traffic. A single Connector is generally capable of handling traffic for hundreds of users, depending on your usage patterns. See Deploying Connectors for more details.

Note: Because Connectors within the same Remote network are interchangeable, it’s important that they all have the same network routing and access rules on the Remote network.

Updated 2 months ago

Remote Networks

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.