Route directory

Global VPN server locations

Exit location affects whether a service is available, while route type determines how traffic travels. Start with the service you need, then narrow your options by region, route type, and use case.

Global Network Coverage

  • 120+countries
  • 220+routes
Exit Locations

Regional Route Directory

Representative cities help you find a region; they are not a current list of data centers. Use cases are starting points, not guarantees that a particular platform will work. Check the user panel for available routes and types.

Asia-Pacific
Country or region Representative city Suggested use
Hong Kong, China Hong Kong Nearby browsing, remote work
Japan Tokyo Japan-specific services, East Asia game servers
Singapore Singapore Southeast Asia business services, collaboration tools

IEPL Hong Kong is the region shown with this route label on the site. Check the user panel for current availability.

North America
Country or region Representative city Suggested use
United States Los Angeles US services, AI tools
Europe
Country or region Representative city Suggested use
Netherlands Amsterdam European services, cross-time-zone work
Routing and Cost

How to Choose a Route Type

The region label shows where traffic exits; the route type describes how it gets there. Even routes with the same exit location may differ in their entry point, cross-border segment, and routing beyond the exit.

Dedicated Transit

IEPL

IEPL is an international Ethernet private line. As a route label, it generally means the cross-border segment uses dedicated transit rather than relying entirely on standard public-internet routing. This can reduce exposure to changes in public routing across that segment, but there is still a path from your device to the entry point and another from the exit to the destination. Congestion on your home Wi-Fi or a slow destination site will not disappear just because you switch to a dedicated route.

Dedicated transit usually requires leased or reserved capacity, which makes it more costly to operate. Video calls, remote desktops, and long uploads are more sensitive to interruptions, so compare dedicated and other route types in the same region. Test a real task during your usual hours, and check how smoothly transitions, screen sharing, and upload completion work—not just the first few seconds after connecting.

Relay Routing

Relay

A relay adds a forwarding hop between the route entry point and its final exit. Your device connects to an accessible entry point, and traffic is then sent along the configured path to the destination region. An extra hop does not always mean a slower connection: if the original public route takes a long detour, the entry point may offer a better path. On the other hand, congestion at the entry point or along the relay segment can affect stability.

Costs for relay routes mainly come from the entry point, relay nodes, and bandwidth between them, so the number of forwarding hops alone is not a good measure of quality. For everyday browsing and routine syncing—or when a direct route repeatedly drops during your usual hours—a relay in the same region can be a useful alternative. Keep the exit region fixed and change only the route type to see whether the difference comes from routing or from how the destination service treats each exit.

Direct Access

Direct

A direct route connects your client to the configured exit node without an additional service-side relay entry point. This does not mean there are no routing hops on the internet: your local provider and the destination network still determine how public traffic travels. A client connecting quickly also does not guarantee that a large file will transfer continuously, since establishing a connection and sustaining a transfer depend on different parts of the route.

Direct routes typically use fewer forwarding facilities and cost less to deploy. For short requests such as web pages, email, and research, start with a direct route that meets the region requirements. If retries happen frequently only at certain times, compare it with a relay or dedicated route in the same region. If just one website has trouble, check your account, service region, and the site’s status before switching exits.

Use Cases

Choose a Route by Use Case

Test in the app you actually plan to use. Keep the device and network connection the same, change one thing at a time, and note where the problem occurs.

Everyday browsing: Check that the whole page loads

If no region is required, start with a nearby exit. Open a site you use regularly and check its text, images, and signed-in features. If the home page loads but details do not, other page resources may be hosted on different domains; that does not necessarily mean the route is unavailable. Repeat the test with another route in the same region. If the difference occurs on only one device, check in the client that the app is using the selected route.

Streaming: Check the catalog, then test playback

Choose the platform and target region, then open the specific title you want to watch. Accessing the platform does not mean the target catalog is available, and seeing a title does not guarantee uninterrupted playback. If the title plays but the picture quality keeps changing, compare route types in the same region and pause background syncing. If the catalog is still different, check your region, account rules, and how the service identifies your exit, then follow the troubleshooting steps in the complete guide to streaming access.

AI tools: Test sign-in, responses, and uploads

First check whether the tool supports the selected region, then use the same exit to sign in, start a conversation, and generate a response. If you need to upload files, test the full process with a small file that contains no sensitive information; opening the home page alone will not confirm that uploads or ongoing responses work properly. If the service reports a region mismatch, check your account and exit location instead of repeatedly switching regions. If disconnections happen only during generation, compare other routes in the same region to avoid confusing account restrictions with connection issues.

Online gaming: Match the game server region

Choose an exit region based on the matchmaking server, not just the location of the game store, download site, or login page. A smooth update download does not mean gameplay will feel responsive. Check for rubber-banding, voice chat dropouts, and reconnects in a training area or unranked mode, and compare routes on the same game server. If problems happen only while someone is downloading or syncing files, check whether your local network is saturated.

Remote work: Keep a backup route for meetings and uploads

Choose a route based on the exit regions and device setup allowed by your organization. Before a meeting, test joining, two-way audio, and screen sharing. For file transfers, check that an upload can run to completion; webpage load times are no substitute. If you regularly access internal company resources, confirm in advance whether a fixed exit or a specific connection method is required. Keep primary and backup routes in the same region where possible, and test switching outside meeting hours to avoid disrupting sessions with a last-minute region change.

Troubleshooting: Identify the scope of the problem first

If the same app still fails after switching routes, check the app or account first. If every app fails on the same route, check your local network and client. If only one region is affected, keep the device unchanged and try another route type in that region. When contacting support, use the support ticket panel to include the region, route type, time of the issue, and the step that failed. Do not include credentials or subscription links.

Start Free