Global routes at a glance

Global nodes and routes overview

VPNDQ covers 120+ countries and 240+ routes, grouped by Asia-Pacific, North America, Europe and other regions. Routes fall into three types — IEPL dedicated lines, relay and direct — and this page explains how each one works, where it fits, and which to pick for your use case.

7-day money-back guarantee Quantum encryption Unlimited devices Alipay / WeChat Pay / USDT
120+Countries 240+Routes UnlimitedSimultaneous devices 7 daysMoney-back guarantee
Asia-Pacific

Asia-Pacific routes

Asia-Pacific is where cross-border access demand is most concentrated. Tokyo and Hong Kong run on IEPL dedicated lines with independent links, suited to long sessions at high bandwidth; Singapore and Seoul use relay routes covering Southeast and Northeast Asia; Bangkok is a direct route that can serve as a backup entry point for Southeast Asia.

Asia-Pacific route list
Country / RegionCityRoute typeStreaming support
Japan Tokyo IEPL dedicated line Netflix / Disney+ / Prime Video
Japan Osaka Relay Netflix / YouTube Premium
Hong Kong Hong Kong IEPL dedicated line Netflix / Disney+ / HBO Max
Singapore Singapore Relay Netflix / Disney+ / Prime Video
South Korea Seoul Relay Netflix / YouTube Premium
Thailand Bangkok Direct Netflix / Prime Video
North America

North America routes

North American routes cover major cities on the US West Coast, the East Coast and in Canada. Los Angeles and Vancouver use relay routes, well suited to US and Canadian streaming; San Jose, New York and Toronto are direct, with fewer hops, suited to scenarios that need a fixed regional exit.

North America route list
Country / RegionCityRoute typeStreaming support
United States Los Angeles Relay Netflix / Hulu / HBO Max
United States San Jose Direct Netflix / Disney+ / Prime Video
United States New York Direct Netflix / HBO Max
Canada Toronto Direct Netflix / Prime Video
Canada Vancouver Relay Netflix / Disney+
Europe

Europe routes

European routes are concentrated in network hubs such as Frankfurt, London and Amsterdam. London and Frankfurt are direct, well suited to local UK and German content; Paris and Amsterdam are relay routes; Zurich, Madrid and Warsaw are direct additions that extend coverage across more of Europe.

Europe route list
Country / RegionCityRoute typeStreaming support
United Kingdom London Direct Netflix / BBC iPlayer
Germany Frankfurt Direct Netflix / Disney+
France Paris Relay Netflix / Prime Video
Netherlands Amsterdam Relay Netflix / Disney+
Switzerland Zurich Direct Netflix
Spain Madrid Direct Netflix / Prime Video
Poland Warsaw Direct Netflix
Other regions

Other regions routes

Routes in other regions cover the Middle East, Africa and South America. Istanbul is a relay route; Cairo, Buenos Aires and Santiago are direct routes that fill in local exit needs for these regions.

Other regions route list
Country / RegionCityRoute typeStreaming support
Turkey Istanbul Relay Netflix / Prime Video
Egypt Cairo Direct Netflix
Argentina Buenos Aires Direct Netflix / Prime Video
Chile Santiago Direct Netflix

The four regions above list only a selection of popular routes. See the full route list inside the client.

Route type

Three route types: how they differ

They all connect, but the link structure behind each route type differs a lot: some run over carrier dedicated lines, some pass through a single forwarding hop, and some connect straight to the exit node. Below we break down how each one works, where it fits and how the costs compare.

Core hubs

IEPL dedicated line

How it works
IEPL is an international Ethernet private line provided by carriers: traffic travels on an independent channel between the entry and exit points and does not pass through congested nodes on the public internet.
Best for
4K streaming, long video meetings, cross-border work, and downloads that need to stay connected for hours.
Cost
The most resource-intensive of the three route types, so it is deployed only in core hubs such as Tokyo and Hong Kong and used as the main route.
Widest coverage

Relay

How it works
The entry server receives traffic first and forwards it to the exit server. The entry point sits closer to the user on a better link, the exit sits in the target region, and the two legs travel over an optimized path.
Best for
Everyday browsing, streaming, AI tools and other bandwidth-heavy uses — also the main way coverage reaches long-tail regions.
Cost
Cheaper than dedicated lines, so relay routes are the most numerous and cover the widest range of regions.
Simplest link

Direct

How it works
There is only one exit server: user traffic connects straight to the exit node with no forwarding hop in between, making this the simplest link structure.
Best for
Scenarios that need a fixed regional exit, plus light browsing, research and signing in to accounts.
Cost
The lowest cost, but quality depends on the international bandwidth of the exit data center, and the gap between regions is more noticeable than with dedicated lines.
Three route types compared
ItemIEPL dedicated lineRelayDirect
Link structureIndependent dedicated-line channel between entry and exitEntry receives traffic first, then forwards it to the exitUsers connect straight to the exit node
Best for4K streaming, cross-border work, long video meetingsEveryday browsing, streaming, AI toolsFixed regional exit, light use
DeploymentConcentrated in core hubs such as Tokyo and Hong KongEntry and exit points chosen separatelyDeployed data center by data center at the exit
Relative costHighestMediumLowest

Route type is not the same as what you can access

Route type only determines the link structure, not whether a given platform will open. The same platform can behave differently on different routes in different regions — if one will not load, switch to another route in the same region first, then consider changing regions.

Choosing a route

Choosing a route by use case

There is no single right answer, but you can narrow it down by what you do. Below are route-type and exit-region suggestions for five scenarios: everyday browsing, streaming, AI tools, gaming and work.

Everyday browsing

Start with the relay route closest to you: Tokyo, Hong Kong or Singapore in Asia-Pacific; Los Angeles or Vancouver in North America; Frankfurt or Amsterdam in Europe. Browsing does not need much bandwidth, and you can switch routes at any time, so there is no need to stay on one.

Streaming

4K streaming holds bandwidth for long stretches, so pick an IEPL dedicated line or a high-quality relay route and stay on it. For US content choose Los Angeles, San Jose or New York; for Japan, Tokyo; for Hong Kong, Hong Kong; for Europe, London or Frankfurt. The same platform can perform differently on different routes — if one will not load, try another route in the same region first.

AI tools

AI tools care more about stability than peak bandwidth: if a long conversation or file upload drops mid-way, you start over. Pick an IEPL dedicated line or a relay route and stay on the same one — when the exit region changes often, some services ask you to verify your login again.

Gaming

Gaming is about latency and packet loss, not bandwidth. Pick an IEPL dedicated line, or a direct route in the same region as the game server, and avoid long paths with multiple forwarding hops. For cross-region play, the closer the exit is to the game server, the better.

Work

Cross-border work usually means video meetings, enterprise cloud storage and internal systems. Pick one IEPL dedicated line or a stable relay route and turn on per-app routing in the client so only the apps that need cross-border access use the route, while everything else stays direct. Simultaneous devices are unlimited, so a computer and mobile devices can share one subscription.

Coverage

Coverage

Routes cover 120+ countries, and the four regional tables above list only some of the popular ones. The client groups all routes by region and lets you search by city name. Below is an index of the exit locations listed on this page.

  • Tokyo
  • Osaka
  • Hong Kong
  • Singapore
  • Seoul
  • Bangkok
  • Los Angeles
  • San Jose
  • New York
  • Toronto
  • Vancouver
  • London
  • Frankfurt
  • Paris
  • Amsterdam
  • Zurich
  • Madrid
  • Warsaw
  • Istanbul
  • Cairo
  • Buenos Aires
  • Santiago

The full route list is the one shown in the client.

FAQ

FAQ

Are routes and nodes the same thing?

No. A node is a specific exit location, and one country or city can have several routes; a route is a single connectable channel. VPNDQ currently covers 120+ countries and 240+ routes, and the same city may have both an IEPL dedicated line and a relay route.

Is an IEPL dedicated line always faster than a relay route?

Not necessarily. A dedicated line's advantage is an independent link with little fluctuation at peak hours; if a relay route's entry point is closer to you, it may feel smoother day to day. Try both once, then settle on one.

Why does switching routes make a platform load?

Each platform has its own rules for judging regional exits, and the same route can give different results at different times and on different platforms. When something will not load, switch to another route in the same region first, then consider changing regions.

Is there a limit on simultaneous devices?

No limit. One account works on computers, phones, tablets and routers at the same time, with no separate subscription for each device.

When does monthly plan data reset?

Monthly plan data resets on your activation day each month; if you upgrade mid-cycle, the price difference is prorated by the remaining days. Data packs last until they run out and never expire, which suits people who do not use the service every month.

For account, payment and client installation questions, see the Help Center.

First Month Free