Global servers and routes

IEPL generally refers to an international Ethernet private line. In a network service, this label indicates that dedicated-line resources are used for the cross-border segment. The path from your device to the access point, and from the egress server to the destination website, may still use public networks. This distinction matters: a dedicated line can help manage conditions on the cross-border segment, but it cannot eliminate local Wi-Fi interference, destination website outages or client configuration issues.

A good fit for use cases where continuity matters, such as long video calls, uninterrupted streaming, remote work and extended sessions with online tools. After connecting, observe performance during the hours you actually use the service: check for repeated disconnects or intermittent pauses rather than relying on the dedicated-line label alone. If your local network is unstable, address the access issue first, then compare routes.

Dedicated lines typically require purpose-built capacity and planning, so their cost structure differs from that of general public network routes. This is a difference in how the routes work; it does not mean VPNUE charges an extra fee for dedicated lines or that all such lines perform alike. See the Plans page for subscription prices. Do not infer pricing or bandwidth guarantees from a route name.

A relayed route sends your connection to an access point first, then forwards it to the selected egress server. This changes how the route is organized; the egress region is still determined by the final server providing external access. Relaying is not a specific protocol and does not inherently mean a slower connection. When the access point and the onward link work well together, the overall experience may be more consistent than a direct connection.

Relayed routes are a useful starting point for everyday browsing, online tools and region-specific content. If a page opens but uploads stall, or the homepage loads but sign-in fails, check whether the issue affects only one service, then try another route in the same region. Keeping the egress region unchanged while switching connection type can help identify whether the issue is related to the region or the path.

Relayed routes require access servers, forwarding resources and onward network connections. Resource costs depend on the route and egress setup. You cannot rank routes simply by counting their hops, and relayed is not another name for a dedicated line. The names on this page are for categorization; when connecting, check the route label in the dashboard and your current experience.

Direct generally means the client connects to the selected egress server without a separate relay entry point managed by the service. “Direct” does not mean there are no intermediate network devices or that the route is physically shorter. Traffic still passes through your local ISP and networks along the way; performance depends on the actual connections between your local access network, the cross-border route and the destination egress server.

If the route between your network and the target region is suitable, a direct connection may work well for everyday browsing or accessing services in that region. However, performance at the same egress server may vary when routes change during peak hours. Test a complete task, such as signing in, opening a document and saving it; do not treat one successful page load as a long-term conclusion.

Direct routes generally require less investment in separate relay resources on the service side, but still involve egress servers and network resources. Lower costs do not necessarily mean lower quality, and a simpler path is not automatically better. Keep suitable options for different needs and switch when necessary instead of treating connection types as a fixed ranking.