Routes and servers

Global server and route overview

VPNAJ covers 120+ countries / 180+ routes, grouped into Asia Pacific, North America, Europe and the rest of the world. The four tables below list representative cities, route types and streaming support for each region so you can pick an entry point by use case; the full list is whatever the client shows.

Start Free View plans
Route overview

Browse route coverage by region

Each of the four regions shows a few representative cities. When a country appears twice, the two routes usually point to different cities and different route types, and they serve different purposes.

01Asia Pacific

Tokyo, Singapore and Hong Kong are the main IEPL exits in this region; Osaka and Seoul add relay capacity, while Bangkok, Ho Chi Minh City, Mumbai and Sydney cover Southeast Asia, South Asia and Oceania.

Asia Pacific routes (selection)
Country/RegionCityRoute typeStreaming
JapanTokyoIEPL dedicatedSupported
JapanOsakaRelaySupported
SingaporeSingaporeIEPL dedicatedSupported
Hong KongHong KongIEPL dedicatedSupported
South KoreaSeoulRelaySupported
ThailandBangkokDirectPartial
VietnamHo Chi Minh CityDirectPartial
AustraliaSydneyRelaySupported
IndiaMumbaiDirectPartial

02North America

The Los Angeles IEPL line is the main trans-Pacific exit; San Jose and New York cover the US West and East Coasts with relay, while Vancouver and Mexico City complete Canada's west coast and northern Latin America with direct routes.

North America routes (selection)
Country/RegionCityRoute typeStreaming
United StatesLos AngelesIEPL dedicatedSupported
United StatesSan JoseRelaySupported
United StatesNew YorkRelaySupported
CanadaTorontoRelaySupported
CanadaVancouverDirectSupported
MexicoMexico CityDirectPartial

03Europe

The Frankfurt IEPL line is the main European exit; London and Paris cover Western Europe with relay, while Amsterdam, Zurich, Stockholm and Warsaw use direct routes for nearby access.

Europe routes (selection)
Country/RegionCityRoute typeStreaming
GermanyFrankfurtIEPL dedicatedSupported
United KingdomLondonRelaySupported
FranceParisRelaySupported
NetherlandsAmsterdamDirectSupported
SwitzerlandZurichDirectSupported
SwedenStockholmDirectPartial
PolandWarsawDirectPartial

04Rest of world

Dubai, Istanbul, São Paulo and Johannesburg cover the Middle East, Latin America and Africa. This region runs on relay and direct routes; IEPL is not deployed here.

Rest of world routes (selection)
Country/RegionCityRoute typeStreaming
United Arab EmiratesDubaiRelayPartial
TurkeyIstanbulDirectPartial
BrazilSão PauloDirectPartial
South AfricaJohannesburgDirect—
Country/Region The country or region where the route lands. Different cities in the same country count as separate routes.
City The city where the exit server sits; the client lists it as City · Country.
Route type IEPL dedicated, relay and direct — the differences and cost gaps are covered in the next section.
Streaming Supported means the route works with major streaming sites; Partial means you need to confirm per platform.
Route type

How the three route types differ

Three labels appear in the same table. They decide which path a route takes, what it is good for, and where the cost sits.

IEPL dedicated01

IEPL dedicated

How it works
An international Ethernet private line — a point-to-point link from the carrier. Traffic enters at a local access point and then travels a fixed cross-border path instead of the public internet's international exit. The path is fixed, so it skips the queuing and detours of the public exit.
Best for
Peak evening hours and sessions that need to stay connected for a long time — AI tool sessions, video calls across time zones, office systems left running all day. In the table, Tokyo, Singapore, Hong Kong, Los Angeles and Frankfurt are the five routes marked IEPL.
Cost
The highest cost per unit of bandwidth of the three, so IEPL is deployed only in the main cities and is the smallest group.
Relay02

Relay

How it works
The client connects first to an entry node near the user, and that entry node forwards traffic over the provider's own links to the final exit server. The user-to-entry leg is short, and the entry-to-exit leg does not depend on detours through the public exit.
Best for
Everyday browsing, video and value-for-money use. When a direct exit gets shaky at peak hours, switching to a relay in the same region is usually the easier fix.
Cost
Between IEPL and direct: the largest group in the route table, and the widest city coverage.
Direct03

Direct

How it works
The client connects straight to an overseas server with no extra hops. The path is the shortest, but it depends entirely on the quality of the public internet's international exit.
Best for
Nearby access, niche routes in specific regions, and a backup entry point for IEPL and relay routes.
Cost
The lowest, which is why it covers the most ground — long-tail countries outside the table mostly run on direct routes.
Picking a route

Choose a route by use case

Every route in a subscription is usable; only the path differs. Below is a priority order for common use cases; if you are unsure, try an IEPL line first, then compare it with a relay in the same region.

01Relay first

Everyday browsing

A nearby entry and fewer hops mean shorter waits when opening pages and searching. If you do not need a specific region, a relay with a closer entry is enough — no need to chase IEPL.

02IEPL first

Streaming

Streaming is sensitive to bandwidth and connection stability. The IEPL routes marked Supported in the table are the first choice; if a title is exclusive to a particular region, check the streaming column for that region before deciding which route to switch to.

03Long connections

AI tools

A chat session is one long connection, and switching routes mid-session breaks it. Pick one IEPL route and stay on it — less hassle than switching constantly; for anything that needs a fixed exit, do as much as possible on that single route.

04Nearest entry

Gaming

Games care about hop count and jitter on the round trip, so a closer entry usually works better. For cross-region play, pick a route in the same region as the game server and do not share it with other uses.

05Stability first

Work

Email, cloud drives and code repositories are all long connections that need reconnecting after a drop. A fixed IEPL path is good for all-day use; simultaneous devices on one account are unlimited, so your phone and laptop can each use a different route.

Coverage

120+ countries / 180+ routes

The four tables above list representative cities only. The full route list lives in the client, grouped by region, and it changes as the subscription updates.

Japan Singapore Hong Kong United States Germany France Netherlands Switzerland Sweden Thailand Vietnam Poland

Coverage is counted as 120+ countries / 180+ routes. One country can have several routes in different cities; for countries and cities not listed here, the client's actual list is the reference.

How to use

How to switch routes

The route list lives in the client, not on this page. Once a subscription is imported, the list updates with it.

Switching in the client

The left column of the client is the route list: click a city name to switch, and use the toggle to connect. The list is grouped by region, and frequently used routes can be pinned to the top. Switching routes does not change your subscription.

Subscription updates

New routes are delivered through the subscription. Update the subscription manually once in the client to get the latest list — no need to reinstall the client; the subscription URL is available in the user panel.

Different routes per device

Simultaneous devices on one account are unlimited. Phone, laptop and router can each pick a route in a different region without affecting one another; clients are available for Windows / macOS / iOS / Android / Linux.

For first-time setup, walk through the quick start guide; if a route will not connect, switch to another one in the same region first, then check each item in the troubleshooting guide. Signing up needs only a username and password — no email address required.

FAQ

Questions about servers

Questions about the route list, switching and updates are collected here; billing and refunds are on the pricing page and in the help center.

Are the routes in the tables all of them?

No. The four tables list representative cities per region to show route types and distribution; the full list is what the client displays, counted as 120+ countries / 180+ routes.

Why does one country have two routes?

Different cities mean different exit servers, and the route type can differ too — Japan, for example, has an IEPL line in Tokyo and a relay in Osaka. Different landing cities suit different jobs: IEPL for long connections and peak hours, relay for everyday browsing.

Do routes change? Do I need to reinstall the client?

The route list updates with the subscription. Update the subscription manually once in the client to get the latest list — no reinstall needed; client version updates and route updates are two separate things.

A route will not connect — what should I check first?

Switch to another route in the same region first to see whether it is one route or the whole region; then work through DNS, per-app proxy and system network permissions in the troubleshooting guide. If every route in the region fails, open a ticket in the user panel with the client version, OS version and the name of the failing route.

Does the route I pick affect data usage?

No. Data is counted by plan and does not depend on which route you pick; monthly plans reset each month on the activation date, and data packs last until used up — they never expire.