100+ Countries / 230+ Routes

Route list: pick an exit by region

VPNPX routes are grouped by region: Asia Pacific, North America, Europe and the rest of the world. A single country may run IEPL dedicated, relay and direct lines at the same time; the difference lies in how the path is built, which tasks it suits and the cost per unit of bandwidth. This page puts the route tables, the line-type notes and a use-case selection guide side by side so you can compare them.

  • 100+ Countries
  • 230+ Routes
  • Unlimited Devices
  • 14-Day Money-Back Guarantee
Start Free View Plans

Route list

Route tables grouped by region

The tables carry static information only: country, city, line type and streaming support. Coverage totals 100+ countries / 230+ routes, and the rows below are representative picks by region. The full list expands by region inside the client, where new routes show up automatically.

Asia Pacific

Asia Pacific routes sit close by, so round-trip latency is low and they carry most everyday browsing and streaming. Hong Kong, Japan and Singapore offer both dedicated and relay lines, while Taipei, Kuala Lumpur and Bangkok are mostly direct.

Asia Pacific routes
CountryCityLine typeStreaming
Hong KongHong KongIEPL dedicatedSupported
Hong KongHong KongRelaySupported
JapanTokyoIEPL dedicatedSupported
JapanOsakaRelaySupported
SingaporeSingaporeRelaySupported
South KoreaSeoulRelayPartial
TaiwanTaipeiDirectSupported
MalaysiaKuala LumpurDirectPartial
ThailandBangkokDirectPartial
AustraliaSydneyRelaySupported
IndiaMumbaiDirectPartial

North America

North America routes mainly serve US content libraries and trans-Pacific work. Los Angeles and San Jose carry most of the traffic, New York and Toronto cover the East Coast, and Vancouver and Mexico City round out the region.

North America routes
CountryCityLine typeStreaming
United StatesLos AngelesIEPL dedicatedSupported
United StatesSan JoseRelaySupported
United StatesSeattleDirectSupported
United StatesNew YorkRelaySupported
CanadaTorontoRelaySupported
CanadaVancouverDirectPartial
MexicoMexico CityDirectPartial

Europe

Europe has the largest and most scattered set of routes. London, Frankfurt, Amsterdam and Paris are the usual exits, Zurich and Stockholm cover Northern and Central Europe, and Madrid, Milan and Warsaw fill in Southern and Eastern Europe.

Europe routes
CountryCityLine typeStreaming
United KingdomLondonRelaySupported
GermanyFrankfurtIEPL dedicatedSupported
NetherlandsAmsterdamRelaySupported
FranceParisRelaySupported
SwitzerlandZurichDirectSupported
SwedenStockholmDirectPartial
SpainMadridDirectPartial
ItalyMilanDirectPartial
PolandWarsawDirectPartial

Other regions

Routes in the Middle East, South America, Africa and Oceania are mostly relay and direct lines. They suit cases that need a local exit, such as checking a local site, comparing regional pricing, or using a service that is only available in that country.

Routes in other regions
CountryCityLine typeStreaming
United Arab EmiratesDubaiRelaySupported
TurkeyIstanbulDirectPartial
IsraelTel AvivDirectPartial
BrazilSão PauloDirectPartial
South AfricaJohannesburgDirectPartial
IndonesiaJakartaDirectPartial
VietnamHo Chi Minh CityDirectPartial
PhilippinesManilaDirectPartial

Exit and content library

Switching routes means switching your exit

When you open an international site, the server sees the country your exit IP belongs to. With an exit in Tokyo the platform returns the Japan catalogue; with an exit in Frankfurt it returns the German one. So switching routes really means switching to an exit in another region: the line type decides how stable the path is, and the exit region decides which content library it leads to.

Content libraries and account regions are two separate things. The platform decides an account's region from its sign-up country and payment method, and changing your exit does not change where the account belongs. To watch a given region's library, the exit has to sit in that region and the account has to be a local account there — both are required.

Platforms also revise their detection rules from time to time. A line that opens a given library today may not do so next month; when one stops working, switch to another line in the same region first rather than changing plans or reinstalling the client.

Line types

How dedicated, relay and direct lines differ

The three line types differ not in protocol but in how data travels from the client to the exit server. Different paths mean different peak-hour behaviour, different best-fit tasks and different cost per unit of bandwidth.

Stability first

IEPL dedicated

How it works
Data travels point to point over a carrier's private network instead of the public internet's international gateways, on a fixed path with dedicated bandwidth. Both ends are joined by a dedicated circuit, so the line does not queue up when ordinary traffic rises.
Best for
4K streaming at peak hours, long video calls, large uploads and downloads, and anything that cannot tolerate a dropped connection.
Cost
The highest cost per unit of bandwidth. At the same price, a dedicated line usually comes with a smaller data allowance than a relay line, so it suits stability-first use with moderate traffic needs.

Balanced value

Relay

How it works
The client connects to a nearby relay entry point, which forwards traffic to the exit server. The entry-to-exit leg runs over an optimised private path that avoids the most congested stretch of the public route.
Best for
Everyday browsing, streaming, AI tools and work across time zones. This is the most common line type in the tables.
Cost
Moderate. For the same data allowance, relay lines offer the best value and are the type to try first by default.

Lowest cost

Direct

How it works
The client connects straight to the overseas exit server with no relay node in between. The path is the shortest, but it relies entirely on public international gateways and is the most exposed to congestion.
Best for
Backup lines, off-peak tasks, and background sync that is not latency-sensitive.
Cost
The lowest. Suits cases where the budget goes on volume and stability matters less.

Choose by use case

Which line to try first across five use cases

Below is a suggested order to try lines for common tasks. Performance shifts with time of day and region, so treat the order as a starting point and adjust it to your own network.

01

Everyday browsing

Start with relay. Page loads care about latency rather than bandwidth, and a nearby relay entry keeps first paint steadier. If pages still load slowly, compare against a direct line in the same region.

02

Streaming video

Relay or IEPL dedicated. 4K needs sustained bandwidth, especially at peak hours; a dedicated line jitters less in the evening, while relay gives better value off-peak.

03

AI tools

Relay. AI tools hold long-lived connections that are sensitive to packet loss, so stay on one line rather than switching often; when a region has several lines, pick the one with the steadiest round-trip time.

04

Gaming

IEPL dedicated or direct. Games are sensitive to both latency and jitter, so check where the game servers sit and pick the geographically closest exit; for cross-region play, prefer a dedicated line.

05

Work

IEPL dedicated. Video calls and cloud document sync need both bandwidth and stability, and a dedicated line's fixed path cuts mid-meeting stutter and reconnects.

Maintenance and switching

Line maintenance and switching

Lines go through scheduled maintenance: data-centre upgrades, exit changes and upstream link work all require short outages. During maintenance another line in the same country takes over, and the list in the client updates itself — no need to re-import the subscription.

This is also why several lines are deployed per country. When one has trouble, switch to another in the same region: the exit region and content library stay the same, only the path changes. Switching happens inside the client, with no sign-out and no re-login.

If several lines still fail to connect, check your local network first, then confirm the client version. If both are fine, open a ticket with the line name and your region so the failing leg can be located.

FAQ

Common questions about routes

What does “Supported” mean in the route tables?

It means the line's exit opened that platform's content library in testing. Platforms change their detection rules from time to time, so support on a given line can change; when it stops working, switch to another line in the same region and try again.

Why does one country have several lines?

A country can host dedicated, relay and direct lines at once, each with a different path and cost. Having several also makes it easy to move to another line while one is under maintenance, with the exit region unchanged.

There are 230+ routes in total — why do the tables show only a few dozen rows?

The tables show representative rows by region, not the full list. The complete set expands by region inside the client, and new lines appear there automatically without manual config updates.

Speeds drop at peak hours — what should I do?

Within the same region, move from relay to an IEPL dedicated line, then compare with direct. If all three are slow, the problem is most likely the leg between your local network and the entry point — try a different network and test again.

How do plans map to lines?

Plans are billed monthly and include a fixed data allowance: ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB, with the allowance resetting each month on the activation date. Lines are switched inside the client; plans are not tiered by the number of lines, and the number of devices online at once is unlimited.

Try Free