GMTVPN Global Routes

IEPL generally refers to a cross-region connection carried over dedicated Ethernet. In subscription services, the term usually describes how part of the path between an entry point and an exit is carried. It does not mean every leg from your device to the destination uses a dedicated network. Home broadband, wireless connections and the path from the exit to the destination service can still affect the experience.

Its value is that the cross-region path can be more controlled, making it suitable for ongoing work sessions, long streaming sessions and interactive tasks. Dedicated capacity typically costs more to procure and maintain, but that cost difference does not guarantee performance to users. To decide whether it is the right choice, compare it on the same local network, with the same target app and at similar times of day.

If an app still stutters, first work out whether the issue is with local access or the destination service's response. A dedicated-route label does not rule out background limits on your device, changing Wi-Fi signal or an app-side problem. For more on transport methods and protocol differences, see route topologies in the protocol guide.

A relayed route sends the connection to an entry point first, which then forwards it to the exit. The goal is not simply to add another leg, but to make use of peering between networks and adjust the cross-region path. If your local carrier has a better connection to the entry point, a relay may provide a steadier route than connecting directly to a distant exit. If the entry point is congested, however, the extra hop can become a bottleneck.

This setup is worth comparing if you want to see how different entry points affect everyday use. Even with the same exit region, different entry points can produce different results, so check both the exit and whether the panel identifies the route type. Relaying adds forwarding and exit-resource costs; actual operating costs depend on the transport and peering arrangements. There is no universal rule that relayed routes fall between dedicated and direct routes.

If performance varies during peak evening hours, keep the target region fixed and try other available routes in the panel, then check whether the app recovers. This helps distinguish a route issue from one on the target platform. See the guide to peak-hour congestion for more context.

A direct route generally means the client connects to the remote access node without an additional relay entry point on the service side. It does not mean there are no intermediate network devices, nor that data always follows the shortest path on a map. Carrier routing, cross-region peering and access conditions at the destination exit all shape the actual path.

When local access and peering to the exit are good, a direct route is worth comparing and is easier to understand structurally. It typically reduces service-side forwarding, but public network access and exit resources still have costs; the route name alone cannot tell you whether a plan should be cheaper. For tasks sensitive to route changes, check whether the connection repeatedly drops during ongoing use, not just whether a webpage opens once.

If a direct route performs poorly in your setup, compare a relayed route in the same region rather than switching straight to a distant exit. Route type and client protocol are separate things: the former describes the path, while the latter describes how the connection is established and carries traffic. Check client compatibility when choosing a protocol. For details, see the protocol and route technology guide.