120+ countries / 210+ routes

VPN Server Locations and International Routes

Compare exit regions and connection methods. Choose a destination first, then select an IEPL dedicated, relay or direct route for your needs.

Region Index

Global Route Guide

The table uses common data center cities to illustrate how regions and route types may pair; it is not a list of available server locations. The suggested uses are tasks you can test when choosing a route, not guarantees of platform availability. Check the client after signing in for the regions and routes currently available.

Representative cities and suggested uses
Country Representative City Route Type Suggested Uses
Asia-Pacific
ChinaHong KongRelayWeb browsing and document access
SingaporeSingaporeIEPL Dedicated RouteVideo calls and persistent connections
JapanTokyoDirectLocal websites and game connectivity checks
JapanOsakaRelayEveryday browsing and uninterrupted playback checks
South KoreaSeoulDirectLocal websites and web apps
AustraliaSydneyRelayRegional websites and cross-border collaboration
North America
United StatesLos AngelesRelayWebsite access and streaming route checks
United StatesSan JoseDirectTechnical documentation and developer services
United StatesNew YorkIEPL Dedicated RouteRemote sessions and cross-border meetings
United StatesSeattleDirectRegional websites and code repository access
CanadaTorontoRelayLocal websites and online collaboration
Europe
GermanyFrankfurtIEPL Dedicated RouteRemote work and online meetings
United KingdomLondonRelayLocal content and web apps
FranceParisDirectRegional websites and everyday browsing
NetherlandsAmsterdamRelayWeb workspaces and file syncing
ItalyMilanDirectLocal websites and online research
SpainMadridRelayRegional content and collaborative documents
Other Regions
BrazilSão PauloRelaySouth American websites and regional content checks
United Arab EmiratesDubaiDirectMiddle Eastern websites and regional business access
South AfricaJohannesburgRelayLocal websites and cross-border collaboration
Connection Methods

Route Types and Cost Differences

A region may offer different connection paths. The comparison below covers common network mechanisms and infrastructure costs; it does not describe 9WVPN speed guarantees or separate billing rules.

Dedicated Transport

IEPL Dedicated Route

IEPL is an international Ethernet private line. When used for an accelerated route, it typically carries traffic over a dedicated segment between the access point and a data center at the other end. The path from your device to the access point and from the exit to the destination website remains separate. In other words, “dedicated line” describes one segment, not an end-to-end private route for every request.

Often worth considering for video calls and remote desktop sessions, where a dropped connection may require reconnecting. Compared with using the public internet directly, a dedicated segment typically involves leasing circuits and planning capacity, which can raise build-out and maintenance costs. To judge whether it suits your needs, check whether full sessions repeatedly reconnect—not just how quickly a page opens the first time.

Multi-Hop Forwarding

Relay Routes

The client first connects to a relay entry point, which forwards traffic to an exit in the destination region. Separating the entry and outbound paths lets you choose a suitable network path for each segment. A relay is worth testing when your provider’s default public internet route performs poorly. If the connection from your device to the entry point is itself unstable, adding a relay may not help.

Useful for web apps, continuous playback and everyday cross-border collaboration. A relay requires additional servers, transmission capacity and maintenance, but its costs are not necessarily the same as leasing a dedicated circuit. To compare, use the same network to access the same destination and check initial page load, subsequent requests and performance over an extended session.

Public Internet Access

Direct Routes

The client connects to an exit server over the public internet without using an additional relay entry point configured by the service. Direct does not mean data passes through only one router, nor does it guarantee that public internet traffic takes the geographically shortest path. Carrier peering and routing changes can both affect the connection.

A good starting point for web browsing, technical documentation and quick lookups, and a baseline for comparing other routes. Skipping a relay layer can usually reduce the associated server and transmission costs. If a direct route handles your tasks on the networks and at the times you typically use it, there’s no need to switch just because another route has a different label. If slowdowns recur, compare a relay or dedicated route while keeping the exit region the same.

Use Cases

Choose a Route for the Task

Testing with your actual tasks is more reliable than guessing based on city names. When comparing routes, keep the device, network, app and destination region the same, and change only one route at a time.

Everyday Browsing: Check Page Loads

If you don’t need a specific region, start with a direct route that connects reliably on your usual network. Test pages you visit regularly, opening the main text, images and internal pages in turn. If the homepage appears but images keep failing to load, the media may use different domains, or browser caching or extensions may be involved. Try another familiar website as a comparison. If both repeatedly fail, test a relay in the same region.

Streaming: Separate Catalog Access from Buffering

First check the platform’s supported viewing regions, account requirements and available titles, then compare routes in the same region. Use the same title and video quality to check playback over time, and try seeking to see whether playback resumes smoothly. If the platform says the content is unavailable, check licensing and your region first. If playback starts but keeps buffering, compare connection methods or check your local Wi-Fi and device decoding.

AI Tools: Check Region and Session Stability

Check the tool’s published service regions and account requirements first, then choose an eligible exit and keep the same region throughout your session. If the site loads but a response cuts off, test a short request and a longer streamed response with the same tool, then compare routes in the same region. For authentication failures, quota limits or platform rate limits, check the app’s message first. Don’t mistake these for a slow connection or keep switching exits to retry. For differences between websites, APIs and developer tools, see the AI Access Guide.

Gaming: Test in Real Matches

Check the game’s region and the client’s supported connection regions first. Choose an exit based on the region you actually play in, not just the city closest to your device on a map. Use practice mode or a non-ranked session to check input response, brief lag and reconnections. If login works but matches remain unstable, check whether game traffic is using the client as expected and whether background updates are using your local network.

Work: Test the Full Workflow First

Check which connection methods your organization permits. For corporate networks and managed devices, follow the configuration provided by your administrator. Before a meeting, use the same device to join, speak and share your screen. For remote collaboration, open a work document, save it and check that it syncs. Avoid switching exits during important sessions. If a backup route passes the same tests, note it and switch before your next meeting or session.