International Route Directory

VPN servers

Browse featured exit locations, see how routes connect across networks, and choose a starting point for your needs.

Start Free View Plans

No email address required. Create an account with a username and password.

Exit Locations

Global Featured Exits

The region and city indicate where traffic exits, not where your device connects to the route. “International route” is a category label; it does not indicate a direct, relayed, or dedicated route. The use-case column suggests scenarios to try and does not guarantee access to any specific app or content library.

Featured international exits
Country / region Featured city Route type Best for
Asia-Pacific
SingaporeSingaporeInternational routeBrowsing Southeast Asian websites
JapanTokyoInternational routeAccessing Japanese websites
Hong Kong, ChinaHong KongIEPL routeTrying a stable connection for extended work sessions
North America
United StatesLos AngelesInternational routeAccessing websites in the western United States
Europe
United KingdomLondonInternational routeAccessing UK websites

Connection routes

Dedicated, relayed, and direct routes

A city tells you where traffic exits; a route type tells you how it gets there. The same exit city can have different connection paths. When comparing routes, consider the exit location and the path separately rather than judging by city name alone.

Dedicated transport

IEPL route

IEPL is an international Ethernet private line that carries traffic between designated endpoints. With this route, the cross-border segment can follow a prearranged path, reducing the impact of changes to some public internet routes. However, the connection from your device to the access point and the one from the exit to the destination service are separate network segments. A weak home Wi-Fi connection or a busy destination website will not be fixed simply by choosing a dedicated route.

Dedicated transport resources generally cost more to build and maintain than standard public internet access. For tasks that can be disrupted by brief packet loss, such as remote desktop sessions and video calls, try a complete session with the same destination over your usual route for comparison. Look for audio dropouts or repeated pauses in desktop controls—not an assumption that anything labeled “dedicated” must be faster.

Forwarded through an entry point

Relayed route

With a relayed route, your device connects to an entry point first, which then forwards traffic to the exit. The benefit is not the extra hop itself, but that this segment may connect to a more suitable carrier network. If your local carrier's public route to the destination region takes a long detour, an entry point with a good connection may improve the overall path. On the other hand, congestion at the entry point or a poor connection from entry to exit can add waiting time.

Relayed routes require extra entry-point resources and forwarding maintenance. They usually cost more than direct routes that maintain only the exit node, though costs also depend on the entry point and cross-border transport. Use a relay as a comparison when a direct route is unstable: keep the exit region the same, switch to a relayed route, and repeat the same task to see whether intermittent slowdowns persist. Relayed and dedicated routes are not mutually exclusive: “relayed” describes how you connect, while “dedicated” describes how one segment carries traffic.

Public internet access

Direct route

A direct route connects your device to the exit node over the public internet, without an additional forwarding entry point. Public internet traffic still passes through carrier networks and routers, so “direct” does not mean the geographically shortest path. When your local carrier has a good connection to the exit, a direct route has a simpler path structure. Performance can vary by time of day when inter-network links are congested.

Compared with adding a relay entry point or purchasing dedicated transport, direct routes are usually simpler to configure and less costly to maintain. Use a direct route as a baseline for everyday tasks like research and email; if browsing is already smooth, there is no need to switch routes just for a different route type. If the same route performs poorly only during your usual hours, test a relay or dedicated route with the same destination and at the same time for a fair comparison.

Route names describe the path, while protocols affect how a connection is established and maintained. Compare exits with the protocol held constant, then compare protocols with the exit held constant, so you can tell which change made a difference. See the protocol guide for how protocols relate to network conditions.

How to test

Choose a route for your needs

First check whether the destination service has location requirements, then test on the device and network you normally use. Change one variable at a time and compare complete tasks; this is more reliable than comparing results from different networks.

Everyday browsing

If the service has no location requirements, start with an exit that is relatively close in network terms. Open a site you use regularly, visit an article, and check that images and page resources load properly. If only one site fails, try other sites in the same region to see whether the issue is site-specific or route-wide. If several sites slow down in the evening, keep the exit region constant and compare different connection paths. Use the same browser and device for each test to avoid interference from cached data or changes to your local network.

Streaming

Check the platform, account, and title's regional rules first, then choose an exit in the relevant region. Loading the home page does not mean a video will play: open the title you want to watch and check startup, continuous playback, and seeking. If you see a message that the content is unavailable in your region, check the region and account requirements first. If it plays but keeps buffering, compare routes in the same region. These are different issues, and switching to a more distant exit may not help. See streaming support for platform information.

AI Tools

Choose an exit based on the service provider's supported regions, then test with your usual tasks. For a web-based chat tool, check whether long responses finish loading. With a coding assistant, try a code completion or a few rounds of edits to see whether the session reconnects repeatedly. If short requests work but longer responses often cut off, keep the exit region fixed and compare connection paths first; then adjust the protocol separately. When signing in, try to keep the same exit so account verification issues are easier to distinguish from network problems.

Gaming

Choose an exit based on the region of the actual game server, not just the region shown in the launcher or store. A fast-loading matchmaking screen does not guarantee smooth movement, voice chat, or in-game actions. Compare direct and accelerated connections in practice mode or a casual match, and watch for rubber-banding, voice dropouts, or latency spikes. If the existing route is already smooth, an extra connection hop may add delay. Switch routes before the next match, not during a game.

Work

Check your company's rules for remote access, sign-in locations, and file transfers before testing your actual workflow. For video calls, check that voice and screen sharing remain stable together; for remote desktop, look for repeated pauses during sustained use; for file sync, confirm the transfer completes. Test your usual route during normal work hours and keep a tested alternative in the same region. Avoid switching routes during a call or upload, as the active session may need to reconnect.