Global Routes and Locations

IEPL generally refers to an international Ethernet private line. It provides a dedicated transport path between designated endpoints, unlike a connection that relies entirely on public internet routing. Traffic travels from your local network to the service entry point, then across the relevant cross-region link to the exit. The final connection to the destination website is still affected by the exit network and the service itself. “Dedicated line” describes the transport arrangement; it does not mean the entire end-to-end connection is reserved for one user.

This type of route can suit work that depends on a consistent connection, such as ongoing use of web tools, remote collaboration or applications with longer sessions. Dedicated transport resources generally cost more to procure and maintain, but that difference does not translate directly into a better experience for every request. Check the dashboard for F4VPN’s current route types and availability. This guide makes no additional price or performance promises based on route type.

A relay route sends a request to an entry point first, then forwards it along another path to the exit. The extra step is intended to provide a more suitable network connection, not simply to make the route longer. Results depend on connectivity from your local network to the entry point, the link between entry and exit, and the capacity of the relay resources. So an extra step doesn’t necessarily mean a slower connection, and the route name alone can’t guarantee greater stability.

For everyday browsing and streaming, a relay route may be worth trying, particularly when direct routing from your local network to certain international exits performs poorly. Relay routes typically involve costs for entry, forwarding and exit resources, so their cost structure differs from direct connections. Performance can still vary when multiple parts of the route are busy, especially at peak times. For a fair comparison, keep the destination, client rules and local network the same, then check page loads and uninterrupted playback—not just the route label.

For connection types, “direct” usually means the client connects to an international exit without an extra relay entry point configured by the service. The route is relatively simple and resource costs are usually easier to manage, but the actual path is still determined by network routing. An exit that is geographically closer may not offer a better route, and “direct” in a route name doesn’t guarantee that your local carrier will always use the same network path.

There’s another meaning to distinguish: DIRECT in routing rules means a request uses your local network to reach its destination without going through the selected international exit. This is often used for local websites and is not the same as a direct international route. If an international site unexpectedly matches DIRECT, check the routing rules. If it matches the selected direct route, check the exit region and the destination service. Distinguishing the two helps you avoid mistaking a rules issue for a route failure.