International Routes · Regional Overview

VPN servers
Routes by region

Choose an exit region first, then compare route types.
Coverage: 100+ countries / 190+ routes.

No email address required. Create an account with a username and password.
Windows / macOS / iOS / Android / Linux. Use your subscription on any number of devices.

Region Index

InternationalRoutes Search Examples

Filter by country or region in the client, then check the city and route type. The table below shows examples of regional searches and route names, not a live availability list or a guarantee that these city and route combinations are always offered. After updating your subscription, check the client for currently available exits, city names, and route types.

Static Examples

“Verify with the target service” means opening the service to check access; it does not guarantee that every route supports the full catalog for that region. On narrow screens, scroll the table horizontally.

Example countries / regions, cities, and route types
Country / Region City Example Route Type Streaming Availability
Asia-Pacific
JapanTokyoIEPLVerify with the target service
JapanOsakaRelayedVerify with the target service
Hong KongHong KongIEPLVerify with the target service
SingaporeSingaporeRelayedVerify with the target service
South KoreaSeoulDirectVerify with the target service
TaiwanTaipeiRelayedVerify with the target service
AustraliaSydneyDirectVerify with the target service
AustraliaMelbourneRelayedVerify with the target service
North America
United StatesLos AngelesIEPLVerify with the target service
United StatesSeattleRelayedVerify with the target service
United StatesNew YorkDirectVerify with the target service
CanadaTorontoRelayedVerify with the target service
Europe
United KingdomLondonRelayedVerify with the target service
GermanyFrankfurtIEPLVerify with the target service
FranceParisDirectVerify with the target service
NetherlandsAmsterdamRelayedVerify with the target service
SwedenStockholmDirectVerify with the target service
Other Regions
BrazilSão PauloRelayedVerify with the target service
United Arab EmiratesDubaiDirectVerify with the target service
South AfricaJohannesburgRelayedVerify with the target service

Region Labels and Actual Exit Locations

When choosing a route, the country or region usually matters more than the city. Websites may determine your location from your exit IP address; city labels mainly help distinguish routes within the same region. A city in a route name does not guarantee precise geolocation, and location databases may disagree. To check, compare the region shown by the target service, the selected option in the client, and the results of your actual connection rather than relying on the name alone.

Coverage describes the overall scale of the service’s international routes; it does not mean every region has every route type at all times. If a city is missing, update your subscription and check for other exits in the same region. If one exit does not work well with a particular service, that does not mean the entire region is unavailable. Try alternatives in the same region first to keep your content region and account environment consistent.

How Routes Work

IEPL, Relayed, and Direct Connections

These terms describe how a connection is routed, not a certified performance ranking. Your experience also depends on your local network, the entry route, the exit, and the target service. Here’s how these routes generally work and when to consider them; refer to the client labels and service information for implementation details.

Dedicated Line

IEPL

IEPL usually refers to an International Ethernet Private Line. In a route setup, a dedicated line can carry traffic across borders between an entry point and an overseas exit, making that segment more controlled. You still connect to the entry point through your local network, and the exit still connects to the destination website, so “dedicated line” does not mean every segment from your device to the service is exclusively yours.

A dedicated line may suit activities that need sustained transfers, such as long video sessions, remote meetings, and ongoing access to work services. Judge it by how well it handles your actual tasks, not by its name. If a page opens but video keeps buffering, check the platform, playback quality, and local network before drawing conclusions from a single issue.

Dedicated lines typically involve additional procurement and maintenance, so their cost structure is often higher than routes using only public networks. This is not a separate billing rule from VPNUI, nor does it mean every dedicated line is faster. VPNUI prices are listed on the plans page; do not infer a dedicated-line surcharge from the route type.

Separate Entry and Exit Points

Relayed

A relayed route first connects to an entry point, which then forwards traffic to the destination exit. The entry and exit serve different purposes: the entry is how your device connects, while the exit determines the region the target service sees. A country such as Japan or the United States in a route name usually identifies the exit, not the entry point’s location.

Relayed routes may suit everyday browsing, research, and app access when you want a convenient connection and a choice of exit regions. A relay may improve the connection between your local network and the exit, but performance can also vary with the entry point, forwarding link, or exit. An extra segment does not necessarily make a route slower or more stable; test it on your own network.

Relayed routes involve entry resources, forwarding, and exit resources. Their costs often fall between different route options, but there is no universal fixed ranking. When choosing, focus on whether the entry is reachable and how the target website performs. If a relayed route in one region does not suit your current network, try another route type in the same region before switching to a distant exit.

Public Network Route

Direct

A direct route usually means the client connects straight to an overseas exit without first using a separate relay entry point. The route is simpler, but traffic still passes through your local ISP and public international networks. “Direct” describes the connection setup; it does not mean the physical distance is shortest or that no network equipment lies along the way.

A direct route may work well for everyday browsing or as a backup when the path from your local network to the target exit performs well. Results can vary by ISP, connection type, and time of day. If a direct route works at home but not on another network, note the difference rather than assuming the country name explains it.

Direct routes generally use fewer dedicated relay resources, but still involve exit and network transit costs. They are not simply “cheaper, so worse” or “one less segment, so faster.” Choose based on whether the route completes your task and stays connected, not on the route label as a quality rating.

Route type and account access are separate things. After updating your subscription, use the options actually shown in the client. Don’t assume this search example means a particular plan includes a particular city, or that IEPL, relayed, or direct routes guarantee streaming access.

Choose by Use Case

Choose a Route by Use Case

Define the task first, then choose a region and route. Keep the target website, device, and network connection the same while comparing; change one route at a time to see what makes a difference.

Everyday Browsing

Check that pages and features work as expected

For everyday browsing, start with a commonly used exit in a region accepted by the target website. Don’t stop at the homepage: open an article, load images, run a search, or view your account page. The homepage may come from cache, so seeing it load does not mean every subsequent request used the right route. If text appears but images or attachments fail, check that the client’s rules send those requests through the same exit.

If the website has no specific region requirements, compare Asia-Pacific exits that work well on your network; a nearby location is not necessarily faster. Keep a backup route that you have tested. If a brief issue occurs, try another exit in the same region first. Frequent cross-region switching can cause the site’s language, content, and account environment to keep changing.

Streaming

Check the region and playback separately

Before streaming, check the target platform’s region requirements, your account access, and the content you want to watch, then choose an appropriate exit. Opening the website, finding a title, and playing the video all the way through are different outcomes. Available content can also depend on platform policies, account settings, and how the exit IP is identified, so the table does not make a blanket availability claim for any platform.

After selecting a route, open the show you want to watch and let it play. Check for buffering, changes in video quality, and whether playback resumes after seeking. Avoid switching regions repeatedly mid-stream; an existing session may continue using the old connection. After changing routes, reopen the playback page and test again. If only one title is unavailable, first check its region and your account access. If several titles on the same platform have issues, compare other exits in the same region. See the Streaming page for more details.

AI Tools

Test sign-in and complete requests

Access to AI tools depends on the service’s supported regions, account requirements, and client routing rules. Choose a region supported by the target service, then test the sign-in page, workspace, and an actual prompt request. A page may load while requests fail due to the service’s account checks, browser session, API requests, or network path; seeing the sign-in page alone does not confirm that everything works.

Stay on a consistent exit where the service permits, and avoid frequent region changes. To compare routes, finish the current request, switch routes, and reopen the page. Test streaming responses, file uploads, and chat history separately, as they may use different endpoints. VPNUI provides international routes, but does not replace the target AI service’s account access, regional policies, or terms of use.

Gaming

Choose an exit based on the game server

Choose a gaming route based on the game server’s region, not just your own location. Account sign-in, game updates, and live matches may use different paths. Being able to access international websites through the client does not mean it handles all traffic for a particular game. Check whether the game and client support the connection method you need, then test it in practice.

When comparing routes, keep the game region and local connection method the same. Check sign-in, matchmaking, match stability, and reconnect behavior. If downloads work but the connection drops during a match, don’t treat download performance as proof that gameplay works. Wi-Fi instability, background uploads, and device resource usage can also affect performance. This page does not guarantee compatibility or specific results for any game. If issues persist, use the Troubleshooting Guide to record what happens.

Work

Keep the exit and session stable

For work, follow your organization’s requirements for remote access, accounts, and devices. Research, cloud documents, meetings, and internal company systems may not need the same route. If you already use a corporate network, don’t blindly stack multiple clients that take over network traffic; conflicting routing or DNS settings can leave public websites working while internal systems become unreachable.

Before an important meeting or long editing session, test sign-in, document syncing, and actual audio and video connections, and keep a tested backup route. Avoid changing exits frequently during work; switching routes may invalidate existing sessions or trigger another verification check. VPNUI supports simultaneous use on any number of devices, but each device still needs the subscription imported correctly and tested. The number of devices is not automatically the cause of a problem, and differences in local settings still matter.

Verify the Connection

Test the connection after switching routes

After choosing a route, consider the client status alongside the result in the target service. A connection indicator only shows the client’s current status; you still need to test the task itself.

Update your subscription, then choose an exit

Check your subscription status in the user dashboard, update the subscription in your client, then expand the region list to see currently available routes. Menu names vary by client, so refer to the interface you see. If an expected exit is missing, check the update result and any error messages; don’t repeatedly import addresses from unknown sources. Your subscription is account information—never post it publicly or share it in a public discussion.

After selecting a route, check that the connection mode and app rules fit your task. If your browser works but an app does not, first check whether it uses the same network path. Manage subscriptions, client downloads, and account status in the user dashboard; this page does not provide installers or subscription URLs.

Get the Client

Record what changed and troubleshoot by symptoms

Before testing, keep your current settings and note the affected service, exit region, route type, client message, and whether the issue occurs during sign-in, loading, or ongoing transfers. Then compare another route in the same region. If only one route fails, start by checking differences between routes. If several regions fail, check your local network, account status, and client configuration.

A support ticket with the steps you took and the comparisons you tried is usually more useful than “nothing works.” Hide subscription URLs, credentials, and private content in screenshots. Never share your account password. If subscription updates fail or the connection repeatedly drops, read the guide first, then add details through the support ticket option in the dashboard.

Open a Support Ticket →