RoutesInternational Route Directory

Global VPN Server Locations

A city identifies the exit location; the route type describes how the connection gets there. Choose an exit region for your needs, then compare direct, relay and IEPL routes in that region.

Browse by Region

International Route Table

The table below shows route examples, not a complete list. The city is the exit location, not necessarily the connection point; for example, choosing a Tokyo exit does not mean the connection also enters the network in Tokyo. Check the client’s streaming labels, and confirm playback on the platform. On narrow screens, swipe horizontally to view the table.

Route examples across Asia-Pacific, North America, Europe and other regions
Country or region City Route type Streaming support
Asia-Pacific
Hong Kong, ChinaHong KongIEPLCheck the client for current labels
JapanTokyoRelayCheck the client for current labels
SingaporeSingaporeDirectCheck the client for current labels
South KoreaSeoulRelayCheck the client for current labels
AustraliaSydneyDirectCheck the client for current labels
North America
United StatesLos AngelesRelayCheck the client for current labels
United StatesSeattleDirectCheck the client for current labels
United StatesNew YorkRelayCheck the client for current labels
CanadaVancouverDirectCheck the client for current labels
CanadaTorontoRelayCheck the client for current labels
Europe
NetherlandsAmsterdamRelayCheck the client for current labels
SwitzerlandZurichDirectCheck the client for current labels
GermanyFrankfurtRelayCheck the client for current labels
United KingdomLondonDirectCheck the client for current labels
FranceParisRelayCheck the client for current labels
Other regions
BrazilSão PauloRelayCheck the client for current labels
ChileSantiagoDirectCheck the client for current labels
ArgentinaBuenos AiresRelayCheck the client for current labels
South AfricaJohannesburgRelayCheck the client for current labels
KenyaNairobiDirectCheck the client for current labels

Start by choosing a country or city that fits your needs, then compare routes in the same region. Changing both the region and route type at once makes it difficult to tell which change caused the difference.

How Routes Work

IEPL, Relay and Direct Connections

Route type describes how traffic reaches the exit. It does not indicate a speed tier or whether the exit IP is dedicated. Cost differences below refer to network infrastructure and operating costs, not VPNHaiLian plan pricing.

IEPL

A dedicated link carries the cross-border segment

IEPL stands for International Ethernet Private Line. In VPN routing, it typically carries a designated cross-border segment; the connection from your device to the access point and from the exit to the destination service may still use public networks. IEPL reduces reliance on public internet routing for that segment, but does not replace your local network or resolve issues with the destination platform.

IEPL routes are worth comparing for video calls, sustained transfers and remote work where a stable session matters. Test with a real task: confirm that you can hear and speak throughout a call, or that a file transfer completes—not just that a webpage opens. Dedicated lines generally involve fixed circuit leases and capacity planning, so resource costs are typically higher than routes using only public networks.

Relay

Traffic passes through an access point before reaching the exit

A relay route first sends traffic to a designated access point, which then forwards it to the exit. This changes the path between your device and the exit, not the region seen by the destination website. A relay is worth comparing when the direct route from your local network to the exit is unstable but the route to the access point is more reliable. Congestion at the access point or along the forwarding segment can also affect the whole connection.

Compare direct and relay routes during your usual usage hours, especially if a site opens occasionally but the connection drops during extended use. Keep the device, exit region and task the same while testing. Relays generally require additional access resources, forwarding capacity and maintenance compared with direct routes. Actual costs depend on each network segment, not just the exit city.

Direct

Connect to the exit over the public internet

A direct route connects the client to the route exit over the public internet, without a designated relay access point on the service side. The path still passes through carrier routing equipment, and a shorter geographic distance does not necessarily mean a shorter network path. Direct does not mean accessing a website without the client; it describes how the client reaches the exit.

Direct routes are useful as a baseline for browsing, looking up documents and short tasks. Try a direct route that meets the region requirement first. If it completes your task on your usual network, there is no need to switch just because another route has a different label. Direct routes generally avoid dedicated-line leases or a designated relay step, but still incur exit, bandwidth and operating costs; route type alone does not determine plan pricing.

Choose a Route for Your Needs

Route Selection Tips

First check which regions the destination service supports. Then consider whether you need brief access, a sustained transfer or a connection that is sensitive to interruptions. Testing on your usual device and network is more useful than opening a page while the network is idle.

Everyday Browsing

If you don't need a specific exit region, start with a direct route to a geographically nearby location. Test search, open an article and load images on sites you use regularly; don't check only whether the homepage appears. Browser cache can make familiar pages load instantly without confirming that new content loads properly.

If several sites slow down at the same time, pause large local file syncs, then compare a relay in the same region on the same device. If only one site has an issue while others work normally, check for a maintenance notice or sign-in issue before switching cities repeatedly.

Streaming

Check the client’s label for the platform, then confirm your account region and the content available there. Opening the platform homepage only shows that the page is accessible; it does not guarantee that a specific title will play. Test the route with the show or movie you actually want to watch, seek once, and wait for the picture quality to stabilize.

If playback starts normally but buffers frequently afterward, keep the title, picture quality and exit region the same while comparing route types. If the player says the title is unavailable in your region, check the platform’s regional policies and your account settings first. Switching to a different route in the same city will not change content licensing.

AI Tools

Check the tool’s supported regions and account requirements first, then choose a matching exit. For a web chat, use a prompt without sensitive information and confirm the response completes. For an editor plugin, test it in the editor you actually use. Accessing the service in a browser does not mean a desktop app uses the same connection settings.

If connections often drop mid-generation, keep the exit region fixed and compare direct, relay or an available IEPL route. If the service reports an account limit or request frequency issue, address the stated cause first. Whether a response is useful and whether the network request completed are two separate questions.

Online Gaming

Check that your account region, matchmaking region and the actual game server region match. Choose an exit near the game server, but don't rely on map distance alone. Routing across different carriers and whether game traffic uses the active connection can also affect performance. Check the game's network rules and client settings before testing.

Test joining a match, continuous gameplay and voice chat in practice or non-ranked modes. If a direct route to the same exit causes stuttering, compare it with a relay in the same region. Avoid switching routes once a match begins; changing exits alters the connection path and may require you to sign in again or rejoin the lobby.

Remote Work

Check your company's network policy and which regions its work systems allow. If a system requires the company intranet or a pre-approved exit, follow the access instructions from your administrator; the route city alone does not determine your access permissions. Test video call audio and video, document saving and file uploads separately.

Keep primary and backup routes in regions approved for work. If calls often drop during your usual working hours, compare relay and IEPL routes under the same conditions. When reporting an issue, note when it occurred, the system or platform, the exit city and what happened. Include only necessary information in a support ticket—never attach login credentials, subscription links or work files.

Start Free