International Route Directory

Global VPN Server Locations

Start with the region you need, then compare connection performance using websites or apps you regularly use. Route labels describe the network path, not a speed ranking.

Coverage

120+ countries / 250+ routes

The table below highlights popular locations; it is not a complete list of servers.

Popular Server Locations

The table groups locations by country or region. Entry points, exits, and access paths may vary within the same location; the location name alone does not identify a data center or route type. We do not associate cities, route types, or platform availability with locations without verification. See the client app for currently available routes.

Popular countries and regions by geographic area
Country or region
Asia Pacific (Asia)
Japan
Singapore
Hong Kong
North America
United States
Europe
Germany
Other (Oceania)
Australia

Dedicated, Relay, and Direct Routes

Route types describe how traffic travels from your connection to its exit. The descriptions below explain the technical differences; they are not a list of route types available in each location. Performance can vary for the same route type depending on your local carrier, time of day, and destination.

IEPL Dedicated Line

IEPL is an international Ethernet private line, typically delivered by a carrier between agreed connection points. Its value is a more controlled transport path than ordinary public-internet transit for that segment. The dedicated line covers only the agreed link, not the entire path from your device to the destination website. Local access and the network between the exit and destination can still affect performance.

Video calls, screen sharing, and interactive work depend on a consistent connection. If public-internet routes fluctuate repeatedly, compare a dedicated line with other paths. Dedicated-line costs typically reflect carrier transport, access at both ends, and capacity planning. The name alone does not guarantee end-to-end speed or that an application will be available.

Relay Routes

A relay route splits the path into an access segment and a forwarding segment: the client connects to a relay entry point, which then forwards traffic to the exit. If the entry point has good peering with your local carrier, this may work better than connecting directly to the same remote exit. The extra forwarding hop can also introduce congestion or become a point of failure.

If a direct connection from your home network to a particular region repeatedly stalls during the hours you use it, keep the same exit region and compare different paths. Relays typically add costs for forwarding infrastructure and link maintenance. Whether a relay is worthwhile depends on whether it improves the part of the route that was causing problems—not on how many locations traffic passes through.

Direct Routes

Here, direct means the client connects to the selected exit server without an additional relay entry point operated by the service. Traffic still travels across carrier networks and public-internet routes; it does not mean there is only one physical hop. The path is simpler and typically avoids the cost of extra relay infrastructure.

For everyday browsing, reading documents, and email, start by testing a direct route. If the same service works during the day but repeatedly stalls in the evening, retest on your usual network at your usual time, then compare other routes to the same region. Changing both the exit location and route makes it difficult to tell which change helped.

Choose a Route for Your Needs

When testing, keep your device, access network, and destination service the same, changing only one thing at a time. How well a route completes the task is more useful than simply seeing “connected” in the client app.

Everyday browsingCheck for consistent loading
Start with a nearby location. Open pages you regularly visit, follow links, and load images. If the homepage opens but later content repeatedly stalls, compare with another familiar site. If only one site has problems, check its service status first; if several are affected, troubleshoot your local network or try another route. A page that opens quickly but frequently disconnects afterward is not a good choice to keep using.
StreamingCheck the region, then test continuous playback
First check whether the platform serves your target region and review its account, catalog, and playback rules. Loading the site, signing in, and streaming a specific title continuously are separate checks. Test the title and quality you plan to watch, including how playback resumes after seeking. If only some titles are unavailable, check licensing and account region first. If several titles buffer, compare your local connection with other routes. See the streaming guide for more tips.
AI ToolsCheck that sessions complete reliably
Check the tool’s published service regions and account rules, then choose an exit location that meets its requirements. Opening the homepage only confirms that the site is reachable. Also check that you can sign in, receive a complete long response, and upload files if needed. For a fair comparison, use the same account and repeat the same task without switching exits mid-session. If you see an account restriction or region notice, consult the platform’s guidance rather than assuming it is a route problem. See the AI tools access guide.
GamingMatch your game region and watch for jitter
Choose a location based on the game region you actually play in, not the address used to download game files. First check input response, voice chat, and reconnection in training or another non-ranked mode. Fast downloads do not guarantee smooth gameplay. If only voice chat is affected, check the game’s voice settings and your local network separately. If movement, ability response, and voice chat all fluctuate, retest with another route near the same game region.
Remote workPrioritize uninterrupted essential tasks
First confirm your organization’s approved connection methods and exit requirements. Test your actual workflow: join a meeting, share your screen, then check cloud documents or remote desktop access. If your organization allows only approved exits, do not switch to another region just to test. Select a route before an important meeting or file transfer, and test any backup route in advance. If everything is working, there is no need to switch routes during work.

How to Troubleshoot Connection Problems

  1. Check your local connection. Turn off the accelerated connection and open a familiar local website to see whether your network is working. Hotel, campus, or guest networks may require you to sign in through a captive portal first. If multiple devices on the same network cannot open ordinary websites, fix local access before troubleshooting international routes.
  2. Check your actual exit. After connecting, open network check to see the exit used by your browser and its reported location. Geolocation databases can be out of date, and the result does not guarantee that a target app uses the same route. If websites work but a desktop app does not, check the client’s connection mode and app rules, then try again in the app.
  3. Keep details you can verify. Note the selected location, time of the problem, access network, and the app’s exact error. A successful route switch shows only that it worked at that moment. If the problem recurs under the same conditions, report it through a support ticket in the user panel. Do not include your password or subscription link.

If you have not finished setting up your connection, follow the getting started guide to import your subscription and test connectivity. Compare routes after the basic checks to avoid mistaking a configuration issue for a regional difference.