Route directory
VPN server locations and international routes
Start with your destination country or region, then filter by route type and use case. The same region does not guarantee the same connection path or streaming support.
Browse regionsBrowse by region
International route directory by region
The cities below illustrate how to search; they are not a confirmed list of available server locations and do not indicate specific route types or streaming support. If the client lists only a country or region, choose at that level. Do not infer the actual exit location from a city in this index.
| Country / region | City (search example) | Route type | Streaming support |
|---|---|---|---|
| Asia-Pacific | |||
| Japan | Tokyo | Check the client | Depends on the selected route |
| Hong Kong | Hong Kong | Check the client | Depends on the selected route |
| Singapore | Singapore | Check the client | Depends on the selected route |
| North America | |||
| United States | Los Angeles | Check the client | Depends on the selected route |
| Europe | |||
| Netherlands | Amsterdam | Check the client | Depends on the selected route |
| United Kingdom | London | Check the client | Depends on the selected route |
| Other regions | |||
| Other countries / regions | Check the client route list | Check the client | Depends on the selected route |
Get the client from the user dashboard · Sign in to access your subscription
Compare connection paths
IEPL, relay and direct routes
Route types describe how a connection is made, not how fast it is. The entry point connects you to the network; the exit point reaches the destination service. The same exit region can have different entry points and transmission paths. When choosing a route, focus on what matters for your task: location, a stable connection or responsive controls.
IEPL private line
IEPL is an international Ethernet private line. For cross-border transmission, it typically carries the international segment of the route, connecting the entry point to the network at the other end. It describes only that segment. Your device's connection to the entry point still depends on local access, and the route from the exit to the destination service depends on subsequent routing. So an IEPL line is not a dedicated end-to-end link from your device to a website.
If long meetings, remote sessions or sustained uploads keep dropping, compare an IEPL route with other routes in the same region. Focus on whether the task completes reliably. Private lines use dedicated link capacity and typically cost more than options that rely on public internet paths. This compares the cost of route resources; it does not mean plans are priced separately by route type.
Relay
A relay route connects through an entry point first, then forwards traffic to an exit in the destination region. The extra hop may avoid a poor public route on your current access network, but it can also become a bottleneck. Neither relay nor direct routes are always better. The same relay route can perform differently on different access networks.
If a direct route connects but often fails while loading pages, streaming or uploading, keep the exit region and switch to a relay route. This makes it easier to see whether the path is the cause. Relays require additional forwarding resources and bandwidth, so their operating costs are typically higher than routes without a dedicated relay entry point. Actual costs depend on deployment.
Direct
A direct route generally connects the client to the selected exit node without an additional, dedicated relay entry point set up by the service. Data still passes through carrier networks and routing equipment. The final path depends on your local network, carrier peering and the destination service's connectivity. A simpler route does not necessarily mean a shorter geographic distance.
For everyday research, reading documents or short visits, start with a direct route as a baseline. If a webpage opens but key actions keep failing, try a relay or IEPL route in the same region. A direct route has one fewer dedicated forwarding step, which can reduce entry-point deployment costs. That does not mean it will respond faster on every network or determine the price of a plan.
When troubleshooting, change one thing at a time. Keep the device, access network and destination service the same while comparing route types in the same region. If the client has no comparable route in that region, account for the regional difference when switching locations; don't attribute every change in results to route type.
Test by use case
Cross-border access: choosing a route
The best way to check whether a route works is to repeat the step that usually fails. A homepage loading does not mean a video will play, and reaching a sign-in page does not mean an attachment will upload. Here are some starting points and when to try another route.
- Everyday browsing
-
If there's no specific regional requirement, start with a direct route in a nearby region. Open a website you use regularly, then follow an internal link or download a non-sensitive file. If the homepage works but resources within the site keep loading, switch to another route in the same region on the same network and repeat the steps. If only one website has a problem, check whether it also fails on other networks before changing settings across all your apps.
- Streaming
-
First check the platform's service regions, account requirements and the content you want to watch. Then see whether the client marks specific routes as supporting streaming. Test with the content you plan to watch: go from the homepage to the playback page, seek through the video and keep watching. If you see a message that the content isn't available in your region, check the account region, exit region and content distribution rights separately. If playback works but keeps buffering, compare routes in the same region and check your local network. These are different problems and shouldn't be treated as one.
- AI Tools
-
Choose a region where the service says it's available, and keep in mind that websites, APIs and accounts may each have their own requirements. Test with a short request that contains no sensitive information, and check that it sends and returns a complete response. If your regular tasks involve attachments, test uploads separately; a working webpage doesn't prove uploads will work. For account permissions, usage limits or server errors, read the message carefully. Frequently switching exit locations usually won't solve these issues.
- Gaming
-
Start with the server region your game actually matches you to, not the region of its store. Test sign-in, matchmaking, controls and reconnecting in training mode or a casual session, paying particular attention to occasional input lag. Smooth update downloads don't mean the route will suit two-way communication during a match. If disconnections happen mostly at certain times, compare routes under the same network conditions and at the same time. Avoid switching routes during a ranked match.
- Remote work
-
First check which connection methods and regions your organization allows. If your company network or remote desktop requires a specific entry point, follow your administrator's instructions. For video calls, cloud documents or remote desktops, test uploads, session stability and whether the app recovers as expected. If you need to keep the same exit location, confirm the route before a meeting or upload. Don't make switching routes a routine step while a task is in progress.