PRIVATE LINK
IEPL
Device → Access point → Dedicated circuit → Exit
IEPL stands for International Ethernet Private Line. An IEPL route uses a dedicated circuit for part of the path between an access point and a remote exit. Compared with routing the entire way over the public internet, this segment is easier to manage. Your device still connects to the access point through the local network, and the exit connects to the destination service over a separate segment. A dedicated circuit does not replace troubleshooting your local Wi-Fi or the destination service.
If you mostly use the service during evening peak hours and calls or sustained transfers repeatedly drop on standard routes, compare them with a dedicated route in the same region. Dedicated routes typically require cross-border circuits, access at both ends, and ongoing operations, so their carrying costs are generally higher than those of standard public internet routes. This compares route infrastructure costs; it does not mean 8LVPN charges separately by route type.
RELAY PATH
Relay Routes
Device → Relay entry point → Exit
A relay route sends traffic to an entry point first, which then forwards it to an exit in the destination region. The extra hop adds another routing step, but the entry point does not have to be in the same place as the exit. If a direct route from your network to an exit often performs poorly, a relay entry point may provide an alternative path. On the other hand, changing exits may not help if the connection between your device and the entry point is unstable.
A relay can be a useful same-region alternative for a specific task—for example, when a streaming library requires a particular region but the corresponding direct route often fails to load fully. Change only the route when comparing options; keep the device, browser, and access network the same. Relays require entry-point resources and forwarding operations. Their costs depend on the path and how it is provisioned, so the “relay” label alone does not determine plan pricing.
DIRECT PATH
Direct Routes
Device → Exit
A direct route connects the client to a remote exit over the current network without an additional relay entry point operated by the service. It does not mean traffic passes through only one device; your internet provider still routes it as needed. Direct routes have a simpler service-side setup and make a good starting point for everyday browsing and troubleshooting. If pages load normally, there is no need to keep switching to more complex route types.
Direct routes generally do not require extra relay resources or a dedicated circuit, so their infrastructure is more straightforward. Performance still depends on the public route between your local network and the remote exit. If a connection works during the day but repeatedly fails in the evening, compare it with a relay or dedicated route in the same region at the same time. If switching access networks fixes the issue, investigate the original network first.