90+ countries / 200+ routes

VPN servers and route selection

A route is shaped by more than its destination. Distance, entry quality, the target service’s region and the time of day can all affect performance. This page presents representative servers by region and explains when IEPL, transit and direct routes are the better fit.

Start Free → View Plans
No device limit 30-day money-back guarantee No email address required
Region and Entry Point

View international routes by region

The table below shows representative regions, cities, route types and streaming suitability. In practice, retrieve currently available servers in the client and choose based on the region of the target website or app.

90+ countries Coverage
200+ routes Entry points
No device limit Device terms
Country or region City Route type Streaming support
Asia-Pacific
Japan Tokyo IEPL Supported
Japan Osaka Transit Choose by target service
Singapore Singapore IEPL Supported
Hong Kong, China Hong Kong IEPL Choose by target service
Taiwan, China Taipei Transit Supported
South Korea Seoul Transit Choose by target service
Australia Sydney Direct Choose by target service
North America
United States Los Angeles IEPL Supported
United States San Jose Transit Supported
United States New York Direct Choose by target service
Canada Vancouver Transit Supported
Canada Toronto Direct Choose by target service
Europe
United Kingdom London Transit Supported
Germany Frankfurt Transit Choose by target service
Netherlands Amsterdam Direct Choose by target service
France Paris Direct Supported
Switzerland Zurich Direct Choose by target service
Other regions
United Arab Emirates Dubai Transit Choose by target service
Brazil São Paulo Direct Choose by target service
South Africa Johannesburg Direct Choose by target service

“Supported” means that the region offers route options intended for streaming. Different platforms apply their own rules based on exit region, account region and content licensing, so actual availability depends on the target service. The route table makes no static promises based on estimated latency, load or bandwidth.

Route Structure

IEPL, transit and direct

Route names describe how data is transported between the local entry point and the international exit. Understanding the structure is more useful than looking at the city name alone when deciding whether a route fits your current needs.

IEPL Dedicated route

Emphasizes control over the entry-to-exit link

IEPL routes typically place the main transport segment between the entry point and international exit on a more controlled link. Compared with relying entirely on ordinary public-network paths, this structure reduces the impact of intermediate routing changes on connection continuity. It suits long sessions, continuous loading, remote collaboration and tasks sensitive to connection fluctuations.

Dedicated-route resources generally cost more to build and maintain than ordinary direct routes, so they are better suited to use cases where stability comes first. Destination still matters: choose a Japan or nearby Asia-Pacific entry for Japanese services, and compare North American dedicated routes with nearby transit routes for North American services rather than choosing solely because a route is labeled “dedicated.”

Long sessions Remote collaboration Video streaming
TRANSIT Transit

Organizes the cross-border path through an intermediate entry point

A transit route sends the connection to a selected entry point first, then onward to the target region. Its value is not simply adding another hop, but avoiding underperforming default international routes and creating a clearer combination of entry point, cross-border segment and exit region. For everyday browsing, AI tools, file syncing and content platforms, transit routes often balance coverage and route cost.

Transit performance depends on the entry point and the target service’s location. For East Asian services, an Asia-Pacific transit route is usually more direct than routing through a distant region. If the target service requires a particular account region or exit area, confirm the destination first and then choose the matching exit. When a transit route does not suit a particular website, switching to another route structure in the same region is often more effective than repeatedly reconnecting to the same server.

Everyday browsing AI tools File syncing
DIRECT Direct

Connects to the exit through a more direct public-network path

Direct routes travel from the current network to the exit server without a dedicated transit entry, keeping the path relatively simple and making it easier to cover more countries and regions. They suit tasks with a specific exit-location requirement, lighter workloads or less common destinations. Because no dedicated transit entry is arranged, performance depends more on the local network, interconnection conditions and public routing to the target region.

Direct does not mean faster in every situation. When the geographic distance is large, cross-network paths change frequently or usage is busy, a nearby transit or dedicated route may be more stable. Conversely, when public interconnection from the local network to the target region is already smooth, direct can complete the task with a simpler path. Judge by whether the task is sustained, whether the destination is fixed and whether the operation remains stable after switching.

Region-specific access Light tasks Backup exit
Use-Case Matching

Route selection tips start with the task

One server does not need to handle every task. Evaluating browsing, streaming, AI tools, gaming and work separately reduces unnecessary switching and makes it easier to find a stable everyday combination.

BROWSE

Everyday browsing

For international websites, research and web forms, start with a nearby region and a stable connection path. Asia-Pacific entry points are usually suitable for routine access from Chinese-language network environments. If the main page opens but images, scripts or login components do not load fully, try another transit or dedicated route in the same region instead of switching straight to a distant exit.

Priority order

Nearby region → Different route types in the same region → Target service region

STREAM

Streaming

Content platforms provide content based on exit region and may also consider account region and licensing territory. First confirm the content region you need, then use a server marked as supporting streaming in that region. If the homepage opens but the playback page does not, switch to another streaming route in the same region and reopen the target app so the connection state and exit region remain aligned.

Priority order

Content region → Streaming support → Backup route in the same region

AI TOOLS

AI tools

AI tools often involve persistent sessions, streamed responses, file uploads and multiple API requests. If any part of the connection changes frequently, responses may stop, pages may wait indefinitely or uploads may fail. Prefer an IEPL or transit route that can reliably reach the target service and sustain a session. Developer tools may also access code repositories, extension marketplaces and command-line services, so exit stability is usually more important than the speed of opening a single page.

Priority order

Service access → Stable long sessions → Continuous uploads and development resources

GAME

Gaming

For gaming, confirm the server region first, then choose a route geographically close to it. Login, updates and gameplay may use different services, so being able to access an account does not guarantee that the later connection is suitable. If fluctuations are noticeable, compare dedicated and transit routes for the same target region. Do not ignore the actual server region simply because city names look similar, and avoid switching exits across regions repeatedly.

Priority order

Server region → Nearby exit → Compare dedicated and transit

WORK

Remote work

Video meetings, online documents, enterprise consoles and file transfers all require continuity throughout the task. Do not experiment with routes after a meeting has started; prepare one regular route and one backup route in the same region in advance. For North American meeting and collaboration services, compare North American dedicated or transit routes first. When team services are concentrated in Asia-Pacific, starting with a nearby Asia-Pacific entry is more sensible.

Priority order

Collaboration service region → Continuous connection → Backup entry in the same region

How to Decide

Use a consistent route-selection process

You do not need to try every server. Narrow the options step by step by target region, task characteristics and route structure to get more repeatable results.

TARGET

Identify the target region first

The target region is the area where the content platform, work service or game server is located, not your current location. Once the region is clear, compare routes within it first and avoid switching across continents without a specific reason.

SESSION

Then decide whether the task is continuous

A standard webpage involves relatively short requests, while meetings, AI chats, file syncing and video playback require a connection that keeps working. For sustained tasks, compare dedicated and transit routes first; for light access, keep direct routes as an option too.

COMPARE

Compare structures within the same region only

Compare IEPL, transit and direct routes in the same region first to see how route structure affects the task. If you change both region and route type at once, it becomes difficult to tell whether the result came from the destination or the transport path.

BACKUP

Keep a backup route in the same region

After choosing a regular route, select another structure in the same region as a backup. If the local network or target-service path changes, you can switch quickly while keeping the exit region broadly consistent and reducing repeated changes to account and content regions.

Usage Conditions

Beyond the route, what else should you check?

A server is only one part of the connection path. Client mode, the local network, target-service rules and subscription status can also affect the final result.

Client routing

Rule mode sends different websites along different paths. If the target app is not included in the proxy rules, switching servers will not change its exit. When an app cannot connect but the browser works, first check whether the app is using the current connection before judging the route itself.

Local network changes

International interconnection paths may differ across access networks. Differences on the same route in different network environments do not mean that the server city has changed. After switching networks, reconnect and complete one full task before evaluating the result; do not rely on a previous short test.

Target service region

Some websites display content or determine feature availability based on exit region. Account settings, content licensing and exit location may all affect the result. For region-specific content, keep the server region aligned with the target region and avoid frequent switching.

Subscription and client status

The server list comes from the subscription configuration. If route names in the client have not changed for a long time, update the subscription and reload the configuration. Windows, macOS, iOS, Android and Linux users must log in and obtain the relevant client and subscription from the user panel.

Start Free