Route coverage · 110+ countries

Server nodes and routes overview

Start Free View Plans

VPNEM routes are grouped into four regions — Asia-Pacific, North America, Europe and Other — covering 110+ countries and 210+ routes, split into IEPL, relay and direct types. This page sets out the path each type takes, the scenarios it suits and how the costs differ, then gives route picks by use case, so you can judge which type fits your scenario before choosing a plan.

  • 60-day money-back guarantee
  • No logs kept
  • No email address required
  • Alipay · WeChat Pay · USDT
  • Unlimited simultaneous devices
Route directory

Server locations grouped by region

Asia-Pacific, North America, Europe and Other: each region lists country, city, route type and streaming support. The table shows a sample of routes; the full list is what you see in the client.

Asia-Pacific ASIA-PACIFIC

Country / RegionCityRoute typeStreaming & AI tools
JapanTokyoIEPL DedicatedNetflix / YouTube
JapanOsakaRelayNetflix / Prime Video
South KoreaSeoulIEPL DedicatedNetflix / Disney+
Hong Kong SARHong KongIEPL DedicatedNetflix / Disney+
Hong Kong SARHong KongRelayChatGPT / Claude
SingaporeSingaporeIEPL DedicatedDisney+ / Netflix
AustraliaSydneyRelayNetflix / YouTube
MalaysiaKuala LumpurDirectYouTube / Netflix
ThailandBangkokDirectYouTube / Netflix
IndiaMumbaiRelayPrime Video / Netflix

North America NORTH AMERICA

Country / RegionCityRoute typeStreaming & AI tools
United StatesLos AngelesIEPL DedicatedNetflix / HBO Max
United StatesSan JoseDirectChatGPT / Gemini
United StatesSeattleRelayNetflix / Prime Video
United StatesNew YorkIEPL DedicatedNetflix / Disney+
United StatesDallasRelayHBO Max / Hulu
CanadaTorontoRelayPrime Video / Netflix
CanadaVancouverDirectNetflix / YouTube
MexicoMexico CityDirectNetflix / Disney+

Europe EUROPE

Country / RegionCityRoute typeStreaming & AI tools
United KingdomLondonIEPL DedicatedNetflix / BBC iPlayer
United KingdomManchesterRelayNetflix / YouTube
GermanyFrankfurtIEPL DedicatedNetflix / Disney+
GermanyBerlinRelayPrime Video / Netflix
FranceParisRelayNetflix / Disney+
NetherlandsAmsterdamIEPL DedicatedNetflix / Prime Video
SwitzerlandZurichDirectNetflix / YouTube
SpainMadridDirectNetflix / Disney+
SwedenStockholmDirectNetflix / Spotify

Other regions OTHER REGIONS

Country / RegionCityRoute typeStreaming & AI tools
United Arab EmiratesDubaiRelayNetflix / YouTube
TurkeyIstanbulDirectNetflix / YouTube
BrazilSão PauloRelayNetflix / Prime Video
ArgentinaBuenos AiresDirectNetflix / Disney+
South AfricaJohannesburgDirectNetflix / YouTube
New ZealandAucklandRelayNetflix / YouTube
What the labels mean: IEPL routes run over a fixed point-to-point channel; relay routes forward traffic through an entry node and an optimized cross-border link; direct routes connect to the international network straight from the local exit. All three types are available in the same subscription — no separate purchase — and the full list plus route switching live in the client.
Route type

Dedicated · Relay · Direct: which type to pick

The three route types are not three price tiers but three ways of organizing the path: they differ in whether the path is fixed, how many times traffic is forwarded on the cross-border segment, and how stable they stay at peak hours.

On any route from your device to a target site, each segment is carried by a different network. The difference between IEPL, relay and direct routes lies in the cross-border segment: IEPL uses a separate point-to-point channel, relay uses a hand-picked optimized link, and direct joins the public routing table.

IEPL Dedicated IEPL

A fixed channel between two endpoints

IEPL is an international Ethernet private line provided by carriers: a logically separate channel between two endpoints, with traffic that never enters the public internet backbone. A fixed path brings two direct results: fewer cross-border hops and less jitter, and no re-scheduling at peak hours, so performance stays much the same as it is during the day.

Best for
Video meetings, remote desktop, real-time gaming, and workflows that need a connection to stay up for hours. If you are sensitive to latency swings and would rather not switch routes by hand, pick this type first.
Cost difference
The highest cost per unit of bandwidth of the three types, so dedicated capacity is concentrated in the cities with the heaviest demand and there are fewer of them than direct nodes.
Relay RELAY

Entry node + optimized cross-border link

A relay route first brings traffic into the nearest entry node, which then forwards it over an optimized cross-border link to the exit node. That is one extra hop compared with direct, and in exchange the cross-border segment runs on a hand-picked link instead of whatever the public routing table decides.

Best for
Web browsing, streaming and AI tools — cases where absolute latency matters less than whether the page or app opens reliably. Relay routes are the most numerous and work well as your default.
Cost difference
Cost sits between dedicated and direct, bandwidth is relatively plentiful, and most regions offer several entry nodes to choose from.
Direct DIRECT

Local exit straight onto the international network

A direct route connects from the local exit straight to the international network with no extra forwarding node. The path is the shortest and the connection comes up fastest, and the exit region matches the city you picked — useful when you need a fixed country exit.

Best for
Lookups, sign-ups and logins that need a specific country exit, and services you want to reach from the nearest point. At peak hours, fluctuations on the public route show up directly on direct routes.
Cost difference
The lowest deployment cost, with the most nodes and the widest city coverage; stability depends on the quality of the local public route, and at peak hours the gap with dedicated routes is clear.
Route typeRoute pathBest forCost difference
IEPL DedicatedFixed channel between two endpoints, no public backboneVideo meetings, gaming, remote desktopHighest; capacity concentrated in key cities
RelayEntry node + optimized cross-border link + exit nodeWeb browsing, streaming, AI toolsModerate; bandwidth is plentiful
DirectLocal exit straight onto the international networkNearby access, fixed-region exitLowest; the most nodes

In the client, every route carries a type label. Switching routes needs no new login and no change to your subscription — just select one and reconnect. All three types draw on the same subscription traffic allowance, so the type you pick does not change the plan price; monthly plans are ¥9.9/60GB, ¥18/250GB and ¥28/500GB, with traffic resetting each month on the day you subscribed.

Route recommendations

Route recommendations by use case

All three route types in one subscription can be switched at any time. Below are five common use cases, which type to prefer for each, and what to check first when a route will not connect.

Five use cases

Browsing, streaming, AI tools, gaming and work each ask something different of a route. Fix one or two routes per use case so you are not testing from scratch every time.

Everyday browsing and research

For pages, documents and search results — many small, scattered requests — prefer a relay route: the entry node is nearby and the cross-border segment runs on an optimized link, so pages open more reliably than over direct. If you only need pages from one specific country, switch to a direct node there. One relay route as your daily default is enough; no need to pick by hand each time.

BROWSE / RELAY

Streaming and 4K playback

Netflix, Disney+ and YouTube care more about bandwidth than latency, and they check the region of your exit IP. Choose relay routes in regions with wider bandwidth, such as Tokyo, Los Angeles or Frankfurt, and confirm before playback that the exit region shown in the client matches the platform you want. For 4K, avoid the hours when your local network is busiest.

STREAM / RELAY

AI tools and API calls

ChatGPT, Claude and Gemini check the country of your exit IP and expect a connection that stays up for a long time. Prefer direct or relay routes on the US West Coast: the exit region is fixed and less likely to look like an unusual jump. Keep the same route while calling an API so a mid-session switch does not break the conversation; more configuration details are in the AI tools guide.

AI / DIRECT

Gaming and real-time matches

Games are far more sensitive to jitter than to average latency. IEPL routes have a fixed path and are not re-scheduled by public routing at peak hours, which makes them the first choice here. When picking a route, check that its region matches the game server region — jitter from crossing continents matters more than the route type itself.

GAME / IEPL

Remote work and video meetings

Meeting tools such as Zoom and Teams are the most sensitive to packet loss and jitter — a stutter usually comes from a swing of a few dozen milliseconds. Switch to an IEPL route before the meeting and leave it unchanged during the call; file sync and remote desktop also do best on dedicated routes, and large transfers can wait for off-peak hours. Step-by-step client instructions are in the full user guide.

WORK / IEPL
What to check when a route will not connect: first try another route in the same region, then another route type (direct → relay → dedicated), and finally check your local network and client version. After switching, give the connection time to come up before judging the result, and avoid switching rapidly one after another.
Coverage

Coverage: 110+ countries / 210+ routes

Asia-Pacific, North America and Europe are the three densest regions; South America, the Middle East, Africa and Oceania are covered mainly through key cities.

Popular regions offer several cities and route types at once: the US West Coast has San Jose, Los Angeles and Seattle, Japan has Tokyo and Osaka, and Europe centers on Frankfurt, Amsterdam and London. Every country has at least one exit city; key cities in Asia and Oceania lean towards dedicated and relay routes, while South America, the Middle East and Africa lean towards relay and direct.

  • Japan
  • Hong Kong
  • Singapore
  • United States
  • Canada
Tokyo Seoul Hong Kong Singapore Sydney Los Angeles San Jose New York Toronto London Frankfurt Amsterdam Dubai São Paulo Johannesburg

The route list grows and changes with demand. The cities on this page are current examples; the full list and availability are shown in the client.

FAQ

Common route questions

Six questions about the route list, route types and traffic cycles.

Is the route list on this page the complete list?

No. The routes listed here by region are a sample, shown to explain how the regions and route types are organized. The full list lives in the client and is added to or adjusted as demand changes; what is actually available in the client is what counts.

Do IEPL, relay and direct routes have to be bought separately?

No. All three types are available in the same subscription, and plans are billed by traffic and period: monthly plans are ¥9.9/60GB, ¥18/250GB and ¥28/500GB, with traffic resetting each month on the day you subscribed. The route type you choose does not change the price — see plans and pricing.

How many routes can be used at the same time?

A subscription allows unlimited simultaneous devices, each choosing its own route, so several devices can connect to different countries at once. One device uses one route at a time; after switching, reconnect for it to take effect.

What happens when traffic runs out?

Monthly plan traffic resets each month on the day you subscribed, and the allowance is restored. If you need more, you can buy a separate traffic pack: ¥158/300GB, ¥358/1000GB and ¥658/3000GB. They are used until they run out, never expire, and stack on top of your monthly allowance.

What should I do first when a route will not connect?

First try another route in the same region in the client, then another route type; most cases are a temporary fluctuation on a single route. After switching, give the connection time to come up before judging the result, and avoid switching rapidly one after another. If several routes in the same region all fail, check your local network and client version, or open a ticket from the user panel.

Can I get a refund if the routes do not meet expectations?

Yes. 60-day money-back guarantee; the conditions and how to apply are in the refund policy. First-time users can start with the quick start guide and follow the steps to import the subscription and test routes one by one.