Server nodes and routes overview
VPNDN routes are grouped into four regions — Asia-Pacific, North America, Europe and Other — and each route lists its city, route type and streaming availability. 100+ countries / 150+ routes site-wide, with unlimited simultaneous devices. This page shows static information only and does not display latency or load figures.
Server nodes grouped by region
The table below groups common routes into four regions: Asia-Pacific, North America, Europe and Other. Each row carries four pieces of information: the country / region of the exit, the city, how traffic on that route is forwarded (route type), and how well that exit works for streaming.
The routes in the table change as data centers and carriers change, so what is listed here are only common examples for each region. The complete, currently available route list is the node list inside the client — log in to the user panel, get your subscription and import it to see it. A single account supports unlimited simultaneous devices, and each device can pick a different route.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Asia-Pacific | |||
| Japan | Tokyo | IEPL dedicated line | Available |
| Japan | Osaka | Relay | Available |
| Singapore | Singapore | IEPL dedicated line | Available |
| Hong Kong | Hong Kong | IEPL dedicated line | Available |
| South Korea | Seoul | Relay | Available |
| Taiwan | Taipei | Relay | Available |
| Malaysia | Kuala Lumpur | Relay | Partial |
| Thailand | Bangkok | Direct | Partial |
| Vietnam | Ho Chi Minh City | Direct | Partial |
| Indonesia | Jakarta | Direct | — |
| India | Mumbai | Direct | — |
| Australia | Sydney | Relay | Available |
| New Zealand | Auckland | Direct | Partial |
| North America | |||
| United States | Los Angeles | IEPL dedicated line | Available |
| United States | San Jose | Relay | Available |
| United States | Seattle | Relay | Available |
| United States | New York | Relay | Available |
| Canada | Toronto | Relay | Available |
| Canada | Vancouver | Direct | Partial |
| Mexico | Mexico City | Direct | — |
| Europe | |||
| United Kingdom | London | Relay | Available |
| Germany | Frankfurt | Relay | Available |
| Netherlands | Amsterdam | Relay | Available |
| France | Paris | Relay | Available |
| Switzerland | Zurich | IEPL dedicated line | Available |
| Italy | Milan | Direct | Available |
| Spain | Madrid | Direct | Partial |
| Sweden | Stockholm | Direct | Partial |
| Poland | Warsaw | Direct | — |
| Turkey | Istanbul | Direct | — |
| Other | |||
| United Arab Emirates | Dubai | Relay | Partial |
| Israel | Tel Aviv | Direct | Partial |
| Brazil | São Paulo | Direct | Partial |
| Argentina | Buenos Aires | Direct | — |
| South Africa | Johannesburg | Direct | — |
| Egypt | Cairo | Direct | — |
“Available” means the exit is commonly used for streaming; “Partial” means regional libraries on some platforms are limited, or the exit only works at certain times; “—” means the exit is not primarily intended for streaming.
How IEPL dedicated lines differ from relays and direct routes
All three route types solve the same problem — moving traffic from your location to an exit data center — but they differ in path, cost and best use. Switch between the tabs below to see how each one works and what it trades off.
100+ countries150+ routesUnlimited devices30-day refund
IEPL dedicated line: point-to-point international Ethernet
IEPL (International Ethernet Private Line) builds a point-to-point dedicated link between the local entry point and the exit data center, so traffic never passes through public internet exchange points and the path stays fixed with minimal jitter. It suits connections that need to stay up for long stretches: video meetings, remote desktop, long AI tool sessions, and streaming that has to keep playing smoothly at peak hours. Dedicated bandwidth costs more than relays and direct routes, so VPNDN concentrates it on the highest-traffic exits instead of spreading it across every route.
100+ countries150+ routesUnlimited devices30-day refund
Relay route: connect to a nearby entry point, then take an optimized cross-border link to the exit
A relay route first connects you to an entry node that is geographically close, and that entry node then forwards your traffic to the exit data center over an optimized cross-border link. Compared with a direct route, it replaces the hardest-to-control leg with a more predictable path, so there is less packet loss and retransmission; compared with a dedicated line it costs less, which is why it can cover more cities. It suits everyday browsing, streaming and office app sync — uses that don't need the lowest possible latency but do need a stable connection.
100+ countries150+ routesUnlimited devices30-day refund
Direct route: the exit connects directly to the target service, shortest path
A direct route connects from the exit data center straight to the target service with no extra relay hops, giving the shortest path and the lowest protocol overhead. The trade-off is that the whole cross-border leg runs over the public internet, so real-world performance at peak hours depends on how congested your carrier's exit is. Direct routes suit sites that are sensitive to the exit region but not demanding on latency, and they also work as a backup when a dedicated or relay route is under maintenance.
Choosing a route by use case
Different uses put different demands on a route: web browsing cares about pages opening reliably, streaming cares about bandwidth and regional libraries, AI tools care about sessions not dropping, gaming cares about round-trip latency, and office software cares about long-lived connections. Below are route suggestions for five scenarios.
Everyday browsing and research
Web browsing is not extremely latency-sensitive, but pages do need to open reliably. Prefer exits that are geographically close and use a relay: Tokyo, Osaka, Seoul or Singapore for Asia-Pacific, Los Angeles or San Jose for North America. A relay replaces the cross-border leg with a predictable path, so looking things up, opening online documents and syncing cloud drives feels more consistent instead of fast one minute and stuck the next.
- Suggested exitsTokyo / Osaka / Seoul / Singapore
- Route typeRelay first, direct as backup
- NoteDon't switch exits frequently during the same session
Streaming and video
Streaming platforms decide which library you can watch based on the region of the exit IP, so a mismatched region means missing content or playback failures. The approach is to pick one exit and stick with it — switching routes mid-episode can look like an unusual login to the platform. On bandwidth, 4K playback needs a steady downstream, and dedicated and relay routes hold up better than direct routes at peak hours.
- Suggested exitsLos Angeles / Tokyo / London / Frankfurt
- Route typeIEPL dedicated line or relay
- NoteKeep the exit region consistent with your account region
AI tools
AI tools are stricter than most websites about access region and session environment: switching exits mid-conversation can trigger re-verification, and a long answer can fail if the connection drops. Keep one dedicated exit for the whole session before considering a switch; when you need long generation runs, prefer an IEPL dedicated line — the path is fixed and jitter is low, so the odds of a mid-run disconnect are lower.
- Suggested exitsTokyo / Singapore / Los Angeles / Zurich
- Route typeIEPL dedicated line
- NoteStay on the same exit for the whole session
Gaming
Gaming is the most sensitive to round-trip latency, and a cross-continent exit adds a noticeable lag between your input and what you see. The rule is to pick the physically closest exit and prefer a dedicated or relay route: Tokyo, Seoul or Hong Kong for Asia-Pacific, Frankfurt or London for Europe. If the game itself is split into regional servers, match the exit region to your server region, otherwise you'll end up connecting to a mismatched server.
- Suggested exitsTokyo / Seoul / Hong Kong / Frankfurt
- Route typeDedicated line or relay
- NoteAvoid cross-continent exits
Cross-border work
Cross-border work needs routes that stay connected for hours: video meetings, instant messaging, email and cloud drive sync often run at the same time. Both relay and dedicated routes can handle this; the key is a stable exit. Having a team share one exit also makes it easier to set up access allowlists in your office systems. Hotel networks vary in quality when you travel, so a low-jitter route is more useful than chasing one specific city.
- Suggested exitsHong Kong / Singapore / Frankfurt / Los Angeles
- Route typeMostly relay, dedicated as backup
- NoteCheck the route works before the meeting starts
Four regions, 100+ countries
Exits are spread across four regions — Asia-Pacific, North America, Europe and Other — and each region has multiple routes that back each other up. Representative cities are listed by region below; the full route list is the node list inside the client.
Asia-Pacific
North America
Europe
Other
Once you have the subscription, the route list lives in the client
Routes are not bought separately: pick any plan, get the subscription link in the user panel and import it into your client, and every available route shows up. Routes added later sync automatically with the subscription.
-
Create your account
Open the user panel and create an account with a username and password. No email address is needed — just pick a name you'll remember, then use it to sign in to the panel and manage your subscription.
-
Choose a plan
Monthly subscriptions come in three tiers: ¥9.9 for 60GB, ¥18 for 250GB and ¥28 for 500GB, with data resetting each month on your activation date. You can also choose a data pack that never expires and lasts until it runs out. Payment supports Alipay, WeChat Pay and USDT.
-
Get the subscription link
Copy the subscription link from the subscription page in the panel. The link works like account credentials — don't forward it to anyone else or post it in public chats or documents.
-
Import it into your client
Import the subscription in the Windows, macOS, iOS, Android or Linux client and the node list appears automatically; when routes are added or removed later, one refresh in the client syncs it.
Plans and refunds
- Monthly plans from ¥9.9, in 60GB / 250GB / 500GB tiers
- Data packs last until used up and never expire
- Unlimited simultaneous devices
- 30-day no-questions-asked refund
- Payment methods: Alipay / WeChat Pay / USDT
- No email address required — a username and password is all you need
Common questions about routes and subscriptions
The most common questions about the route list, choosing a route and getting a subscription. Answers follow the current plans and refund policy.