This page explains locations, route types and traffic rules. Check your subscription after logging in to see the servers and labels available to your account.
REGIONS / READING EXAMPLES
Browse routes by region
The table below shows examples of locations and route types. It is neither a complete list of coverage nor a current list of available servers. A city can have multiple routes, and the same city name does not guarantee the same entry point, exit point or experience.
On narrow screens, swipe horizontally to view the table. Streaming support is qualified rather than inferred from a location name.
Examples of locations and route types; check your subscription for actual availability
Country
City
Route type
Streaming support
ASIA PACIFIC
Japan
Tokyo
IEPL dedicated line
Depends on the actual route and the platform’s region detection
Japan
Osaka
Relayed
Depends on the actual route and the platform’s region detection
Singapore
Singapore
IEPL dedicated line
Depends on the actual route and the platform’s region detection
South Korea
Seoul
Relayed
Depends on the actual route and the platform’s region detection
Malaysia
Kuala Lumpur
Relayed
Depends on the actual route and the platform’s region detection
Thailand
Bangkok
Direct
Depends on the actual route and the platform’s region detection
Australia
Sydney
Relayed
Depends on the actual route and the platform’s region detection
New Zealand
Auckland
Direct
Depends on the actual route and the platform’s region detection
NORTH AMERICA
United States
Los Angeles
IEPL dedicated line
Depends on the actual route and the platform’s region detection
United States
Seattle
Relayed
Depends on the actual route and the platform’s region detection
United States
New York
Relayed
Depends on the actual route and the platform’s region detection
Canada
Toronto
Relayed
Depends on the actual route and the platform’s region detection
Canada
Vancouver
Direct
Depends on the actual route and the platform’s region detection
EUROPE
United Kingdom
London
IEPL dedicated line
Depends on the actual route and the platform’s region detection
Germany
Frankfurt
Relayed
Depends on the actual route and the platform’s region detection
France
Paris
Relayed
Depends on the actual route and the platform’s region detection
Netherlands
Amsterdam
Direct
Depends on the actual route and the platform’s region detection
Sweden
Stockholm
Relayed
Depends on the actual route and the platform’s region detection
Switzerland
Zurich
Direct
Depends on the actual route and the platform’s region detection
OTHER REGIONS
Brazil
São Paulo
Relayed
Depends on the actual route and the platform’s region detection
Chile
Santiago
Direct
Depends on the actual route and the platform’s region detection
South Africa
Johannesburg
Relayed
Depends on the actual route and the platform’s region detection
United Arab Emirates
Dubai
Relayed
Depends on the actual route and the platform’s region detection
India
Mumbai
Direct
Depends on the actual route and the platform’s region detection
What country and city labels tell you
Location labels help you identify the intended exit region. They do not necessarily match the region a service assigns to your account, and they cannot confirm where physical equipment is deployed. Platforms may consider IP address databases, account settings, payment region and session history, so the city shown in your client may not match the region displayed by a platform. If they differ, check the actual exit and the target app’s response rather than relying on the server name alone.
Coverage describes the range of international routes you can choose from; it does not mean every location is right for every use. Nearby exits are often worth trying first, but performance depends on the route from your local carrier to the entry point, the international transit segment and the route from the exit to the destination site. First choose a candidate that meets the app’s regional requirements, then compare it in consistent use. There is no need to keep switching to farther locations just for the sake of it.
TRANSPORT / COST / CONDITIONS
Dedicated lines, relayed and direct routes
Route types describe how a connection is arranged, not how well it performs.
These descriptions cover general principles behind each route type. Check your subscription for the actual entry point, route details and available types; the name alone cannot tell you how the full connection will perform.
PRIVATE TRANSPORT
IEPL dedicated line
This usually means the international transit segment uses Ethernet leased-line resources. That segment works together with local access, the international exit and the connection to the destination service to form the full route. It does not mean every segment between your device and the website uses a dedicated line.
PATH
Dedicated line for the international segment
SCENE
Sustained sessions and work
COST
Dedicated-line resources generally cost more
Worth considering when route stability is a priority. Actual performance still depends on your local network, congestion at the entry point, exit quality and the destination platform’s status.
RELAY TRANSPORT
Relayed
Requests reach an entry point first, then pass through an intermediate node to the destination exit. By arranging the transit segments, a relay can improve the route between some local networks and remote exits. It adds a hop, however, and another connection segment to maintain.
PATH
Traffic is forwarded through an intermediate node
SCENE
Everyday browsing and streaming
COST
Depends on the entry point and forwarding resources
Useful to compare when balancing location choice with everyday performance. A relayed route is not inherently slower than a direct one, and route quality cannot be judged by the number of hops alone.
DIRECT TRANSPORT
Direct
Here, direct means the client connects to the selected international node without an intermediate relay, typically relying more on your local carrier and public internet routing. The route is simpler, but the actual path across borders depends on network conditions. A geographically closer location is not necessarily the best fit for your connection.
PATH
Client connects directly to the node
SCENE
Everyday connections with a good route
COST
Typically uses one fewer forwarding resource
A good option when the public internet route from your local network to the destination region performs well. A direct international route is not the same as a local direct connection in traffic-splitting rules.
Differences in operating costs do not determine plan pricing
Dedicated lines involve purchasing transit resources, relayed routes also need entry and forwarding resources, while direct routes rely more on public internet paths. These points help explain operating costs; they do not mean D6VPN charges separately for a particular route type. Check the plan page for data allowance, billing period and the locations available to your account. Do not infer prices from route names or assume a dedicated-line label means you have exclusive use of the entire transit resource.
How traffic rules and route types differ
Traffic rules determine whether a request needs an international exit and which policy handles it. Route types describe how the selected international connection is arranged. When a local site connects directly through your local network, an international app may use the selected node instead. Different apps on the same device using different exits is normal with traffic splitting. The IP shown by a local website does not represent every app’s connection.
Bank-grade encryption helps protect the connection, but it does not replace security measures on the websites you use. Whether you choose an IEPL dedicated line, a relayed route or a direct route, protect your password and subscription details. For services that require a login, also pay attention to platform prompts; not every verification issue is caused by route quality.
APPLICATION / ROUTE DECISIONS
Choose an exit for your needs
First check the target service’s regional requirements, then limit other variables. Change just one route or rule at a time to make it easier to identify the cause of a problem.
BROWSING
Everyday browsing: keep local traffic direct
Local sites, research and international websites do not usually need to share the same exit. Start with rules that match traffic by app or domain, check whether the target page loads fully, and then decide if you need a different international route. If text loads but images or attachments do not, some page resources may use different domains; check which rules handle those requests.
For sites without a specific regional requirement, start by comparing nearby locations with suitable routes. Page load times also depend on the site’s servers, browser extensions and local Wi-Fi. Do not rank every route based on a single page load, and there is no need to send local traffic through an international exit as well.
STREAMING
Streaming: check the catalog, then test playback
A streaming platform’s catalog, account entitlements and region detection are separate factors. Choose a target region, then check the catalog and playback in practice; a route’s location does not guarantee that a platform will allow playback. Even if the platform homepage opens, that does not mean a particular title, resolution or all content will be available.
For playback, sustained data transfer matters more than how quickly the page first opens. If buffering keeps recurring, pause large downloads on other devices, check your local network, then try another available route in the same region. After changing exits, you may need to start a new app session; follow the platform’s instructions. For more on catalogs and playback conditions, read our guide to choosing a Netflix region.
AI TOOLS
AI tools: keep your region and session consistent
Before using ChatGPT, Claude or another AI tool, check the platform’s current supported regions and account requirements. An international route addresses the connection path; it does not replace platform authorization or guarantee an account review outcome. A node that opens an information page may not meet the same requirements for signing in, chatting, uploading files or making payments.
Where the service is available, try to keep the exit location consistent rather than switching regions repeatedly within one session. If you see a verification prompt, note its wording and when it appears, check your browser session and account status, then decide whether to change routes. For more on how location detection works, see our AI guide.
GAMING
Gaming: match the server region and client support
First check the game server’s region, then make sure your client supports the connection method the game actually uses. Downloads, login authentication, matchmaking and gameplay may connect to different services, so completing a download does not prove that match traffic is routed correctly. Check the game’s connection feedback and performance over sustained play rather than relying on smooth web browsing.
When comparing routes, use the same local network and game server where possible, and close background downloads or other potential sources of interference. If changing routes does not help, check your Wi-Fi signal, background tasks on your device and the game service’s status. A general international route is not a dedicated service optimized for every game; this page does not promise compatibility with all games.
WORK
Work: keep business sessions stable
Remote meetings, cloud documents and cross-border business dashboards may respond differently to changes in your exit. Before handling important work, check your company’s or platform’s access policies, then choose an available route in a permitted region. For corporate networks or managed devices, follow your organization’s configuration requirements rather than overriding existing network policies.
Once a long meeting or business session is underway, avoid changing exits if possible. If a platform requires a fixed address, first verify that the service actually meets that requirement; selecting a particular node does not mean you have an exclusive or permanent address. Unlimited devices describes how many devices can connect, not exclusive use of transmission resources. When several home devices stream or download at once, keep local network congestion in mind.
CHECK / COMPARE / RECORD
What to check after connecting
Confirm the rules are working before comparing routes.
Check your subscription and current selection
After logging in, get your subscription and confirm in the client that it updated successfully and the selected policy includes the target node. Subscription details may change during route maintenance, so an old list may not reflect current availability. Once updated, check the active policy to make sure requests are not still handled by another one, even if the new node appears in the interface. For initial setup, follow the setup guide to import your subscription and authorize the client.
Check the result in the target app
Open the website or app you actually need and check sign-in, content loading and key actions. Remember that the page you use to check your exit is also affected by traffic rules: a local direct connection showing your local exit does not mean an international app is not using the selected route. Compare your IP lookup with the client’s rule-matching information as troubleshooting clues, not as a definitive verdict on every request path.
Record the conditions; avoid blind retries
If something goes wrong, note your device platform, local network, node name, client mode, target app and the exact message. Try another actually available route in the same region before deciding whether to change regions. This can reduce repeated changes to your account region and help distinguish a route issue from a platform-side problem. When submitting a support ticket, include these details. Never share your password, full subscription URL or other account credentials on a public page.