VPN server locations
and international routes

IEPL generally refers to an international Ethernet private line, using dedicated cross-border transmission resources to establish a connection. Compared with routes that rely mainly on the public internet, it offers more controlled resource allocation across the international segment and may suit users who value a consistent connection. This site’s examples include IEPL routes to Hong Kong and the United States; check the client to confirm the actual exit location.

Dedicated routes generally cost more to build and maintain, which is one reason route types have different cost structures. However, a route labeled IEPL does not mean you receive dedicated bandwidth, nor does it mean the entire connection from your device to the destination uses a private line. Congestion on your local Wi-Fi or a slow destination server can still affect performance.

For video calls, remote collaboration and work that depends on maintaining a session, IEPL is worth comparing first. Focus on whether the connection stays up, audio remains clear and interactions stay responsive over time—not just peak download speeds in a brief test. If your local network is unstable, check your connection environment before deciding whether a dedicated route helps.

A relay route forwards traffic through an intermediate node between your device and an overseas exit. The entry point receives the connection and passes it along to the exit. This does not simply reduce physical distance; it organizes access through different network entry points and forwarding paths. Japan relay is one example shown on this site. Check the full route name before use so you do not mistake the entry region for the final exit.

Relay routes incur resource costs for the entry point, forwarding and exit, and their performance depends on how these parts connect. An extra relay may improve an otherwise poor public route, but it can also add latency if the forwarding location is a poor fit. Do not judge a relay by its name alone; compare it with other route types on your local network.

Try a relay route for everyday browsing, access to sites in other regions, or when a direct route feels inconsistent. Keep the destination site and steps the same while comparing: first check whether the page loads fully, then see whether access remains stable. If changing only the route type improves the experience, that is usually a more targeted fix than buying more data.

A direct route generally means the client connects to an overseas node over the public internet, without an additional relay entry point arranged by the service. “Direct” describes how the connection is set up; it does not mean the path is always the shortest or that every website is accessed directly from your local network. Whether traffic uses a subscription route also depends on the client’s current routing rules.

Compared with dedicated routes, direct connections generally rely less on dedicated transmission resources and have a different cost structure. They are more likely to be affected by your local carrier’s international gateway, public routing choices and time of use. A direct route may work well on a compatible access network, but performance can change on a different network.

The Singapore direct route shown on this site makes a useful point of comparison. Do not rule out direct routes in advance, but do not assume fewer relays always mean better speed. Test the connection with your actual tasks, then compare it with relay or IEPL and keep the option that suits your current network. Route operating costs are not the same as plan prices; see the plans page for billing.