ROUTE TYPES
How the three route types work
Route names describe how data is organized as it enters an international link from the local network. There is no universal ranking outside a specific use case: stable tasks usually benefit from controlled paths, short browsing sessions from regional matching, and long-distance access from checking where the target service is actually deployed.
TYPE A
IEPL
A more controlled international path
IEPL routes carry cross-border traffic over more tightly controlled international links, reducing repeated path changes across the public internet. The focus is not a one-time peak speed test, but making paths for long-lived connections, sustained transfers, and busy periods more consistent.
These routes suit video calls, remote development, continuous AI conversations, code repository sync, and high-bitrate streaming. Because link resources and routing costs are typically higher, reserve them for interruption-sensitive tasks rather than sending every connection through the same endpoint.
PATH POLICY
LOCAL
IEPL
DEST
TYPE B
Relay
Connect through an optimized entry point first
Relay routes send the connection to a more suitable entry point first, which then connects to the target region. This adds a routing layer, but can avoid an unsuitable direct path between the local exit and the remote network. For balancing coverage, cost, and stability, relay routes are often the most versatile option.
Everyday websites, file downloads, social platforms, and most streaming tasks can start with a relay route. If a route loads pages slowly, leaves images incomplete, or repeatedly rebuilds long connections on your current network, try another relay entry in the same region instead of switching straight to a more distant country.
RELAY POLICY
LOCAL
HUB
DEST
TYPE C
Direct
Connect directly to the target region
Direct routes travel from the local network to the target region without an extra relay layer. Their simpler structure suits strong local exits, nearby destinations, or tasks that do not require a persistent connection. They also make it easier to assess the baseline connection quality between your network and a given region.
Direct routes depend more on the local carrier network and public international paths, so the same city may perform differently across networks. They are usually a lightweight choice for everyday browsing and a useful comparison for troubleshooting: when direct and relay routes differ noticeably, the issue is often the path rather than the client settings.