Global Route List & Node Coverage
VPNHP operates 250+ routes across 120+ countries, grouped by Asia-Pacific, North America, Europe, and other regions. This page lists representative routes with their country, city, route type, and streaming support, and explains how IEPL dedicated lines, relay, and direct routes work and where each fits, so you can check them before choosing a plan or a route.
Coverage & Route Mix
The network blends three route types: the busiest directions (Tokyo, Singapore, Los Angeles, London, and more) run on IEPL dedicated lines to guarantee quality on the cross-border leg; secondary directions are served by relay routes, balancing quality with coverage; long-tail regions use direct routes to widen country coverage. How each type works, where it fits, and what it costs is covered in the Route Types section below.
The route list is maintained server-side: additions, adjustments, and maintenance all happen on the server, and clients sync the latest list automatically after updating the subscription. The tables on this page show representative routes only — the authoritative list is what your client pulls from the subscription, and cities not listed here may still be in service.
One subscription comes with unlimited devices: sign in with the same account on Windows, macOS, iOS, Android, and Linux clients and you see the same route list, so you can switch routes on any device following the advice on this page.
Asia-Pacific
North America
Europe
Other Regions
Route List by Region
The tables below group representative routes by region. Route Type covers three kinds: IEPL dedicated line, relay, and direct. The Streaming column shows whether the route has been verified for streaming scenarios — a "—" means unverified, not necessarily unusable. On narrow screens the tables scroll horizontally.
Asia-Pacific APAC
| Country / Region | City | Route Type | Streaming |
|---|---|---|---|
| Japan | Tokyo | IEPL | Yes |
| Japan | Osaka | Relay | Yes |
| South Korea | Seoul | IEPL | Yes |
| Singapore | Singapore | IEPL | Yes |
| Hong Kong | Hong Kong | Relay | Yes |
| Thailand | Bangkok | Direct | — |
| Malaysia | Kuala Lumpur | Relay | Yes |
| Philippines | Manila | Direct | — |
| Indonesia | Jakarta | Direct | — |
| Australia | Sydney | Relay | Yes |
North America NA
| Country / Region | City | Route Type | Streaming |
|---|---|---|---|
| United States | Los Angeles | IEPL | Yes |
| United States | San Jose | IEPL | Yes |
| United States | Seattle | Relay | Yes |
| United States | New York | Relay | Yes |
| Canada | Vancouver | Relay | Yes |
| Canada | Toronto | Direct | Yes |
Europe EU
| Country / Region | City | Route Type | Streaming |
|---|---|---|---|
| United Kingdom | London | IEPL | Yes |
| Germany | Frankfurt | IEPL | Yes |
| France | Paris | Relay | Yes |
| Netherlands | Amsterdam | Relay | Yes |
| Switzerland | Zurich | Direct | — |
| Sweden | Stockholm | Direct | — |
| Italy | Milan | Direct | Yes |
| Spain | Madrid | Direct | — |
Other Regions MENA · LATAM · AF
| Country / Region | City | Route Type | Streaming |
|---|---|---|---|
| United Arab Emirates | Dubai | Relay | — |
| Türkiye | Istanbul | Direct | — |
| Brazil | São Paulo | Relay | Yes |
| Argentina | Buenos Aires | Direct | — |
| South Africa | Johannesburg | Relay | — |
| India | Mumbai | Direct | — |
These are representative routes. For the full list (120+ countries / 250+ routes), update your subscription in the client app — the list syncs automatically with server-side adjustments.
Route Types Explained: IEPL / Relay / Direct
The core difference between the three types is how the cross-border leg is handled: a dedicated line is exclusive end to end, a relay adds one optimized forwarding hop, and a direct route goes straight through. The type sets the route's cost and stability ceiling, and determines which directions it should serve. Details below.
IEPL Dedicated Line
Cost · HighHow it works: IEPL (International Private Leased Circuit) means the cross-border link between the entry point and the destination data center is a dedicated circuit with exclusive bandwidth — it does not transit the public internet backbone. Packet loss and jitter on the cross-border leg are bound by the circuit's service-level terms and do not fluctuate noticeably with public-network congestion during evening peaks.
Best for: Workloads that need sustained bandwidth and stability — HD streaming, video conferencing, large file transfers, and long-term use where the experience must not degrade at peak hours.
Cost difference: Dedicated lines are billed by bandwidth and are the most expensive of the three, so they are typically deployed only on the highest-traffic directions such as Tokyo, Singapore, Los Angeles, London, and Frankfurt.
Relay Route
Cost · MediumHow it works: Traffic between the entry point and the destination data center passes through one relay server: the client connects to the relay node first, the relay optimizes transmission quality on the cross-border leg, and the destination data center then reaches the target site. Compared with a direct route, the extra hop buys a steadier cross-border path.
Best for: Everyday browsing, standard-definition streaming, AI tool access, and most other uses — a balance between quality and coverage, and the type with the most cities served.
Cost difference: No exclusive end-to-end bandwidth is needed, so costs sit between dedicated and direct. Relays are well suited to secondary directions, bringing more cities into the service area.
Direct Route
Cost · LowHow it works: The client builds an encrypted tunnel straight to the destination data center with no relay in between. It has the simplest link structure of the three, the fewest intermediate nodes, and the exit is the destination data center itself.
Best for: Lightweight uses that don't need much bandwidth, and cases where you want a fixed exit with as few link layers as possible; when accessing local services in the destination country, a direct exit is the most straightforward option.
Cost difference: The cheapest of the three, usually deployed in long-tail regions to push country coverage past 120+, so even niche destinations have a usable exit.
Choosing a Route by Use Case
There is no one-size-fits-all route. Two basic rules: pick the type by your main use case, and pick the city by physical distance. Below are suggestions for five common use cases — a good starting point, but real-world experience should be judged by comparing routes one by one in the client app.
Everyday Browsing
Start with a relay route and pick an Asia-Pacific node close to your location — load speed and stability usually have headroom to spare. If pages stutter noticeably, switch to an IEPL dedicated line in the same region to compare, so you can tell whether it's the route or the site itself.
HD Streaming
Streaming is sensitive to sustained bandwidth and packet loss. Prefer IEPL dedicated lines marked "Yes" for streaming in the tables; if your region has no dedicated line, use a relay in the same region and enable traffic-splitting rules in the client so other traffic doesn't eat the bandwidth.
AI Tools
Services like ChatGPT and Claude care about exit IP quality — prefer dedicated or relay routes in the United States, Japan, or Singapore. If you hit an "not available in your region" message, try another city in the same country first, then another country; that resolves most cases.
Online Gaming
Games are the most sensitive to latency and jitter. Pick the dedicated line physically closest to you — the shorter the cross-border leg and the fewer the intermediate nodes, the lower the latency floor. Avoiding large downloads on other devices during gaming sessions helps more than repeatedly switching routes.
Remote Work
Video meetings and intranet systems need long, stable connections — prefer a dedicated line, and connect plus verify once before the meeting starts. Work traffic is usually light: the 60GB monthly plan (¥9.9/month) covers most work scenarios.
Route Selection FAQ
Does the route list change?
What if a route won't connect?
What does a "—" in the Streaming column mean?
Can multiple devices connect at the same time?
I'm not familiar with route types — is there a low-effort approach?
For route switching and subscription import steps on each platform, see the quick start tutorial.