Server Locations - VPNDU | 100+ Countries / 250+ Routes

COVERAGE

Coverage and route mix

The 250+ routes aren't just a number on a list — they fall into three types by use case: IEPL dedicated lines for HD streaming and live events, relay routes covering most everyday scenarios, and direct routes for budget-focused users. All three share one subscription and can be switched at any time in the client, so there's no need to buy separately for different uses.

100+ countries and regions
250+ routes
Unlimited simultaneous devices
7 days money-back guarantee

Below are the regions and cities that appear in the route table on this page. The complete route list is whatever the client actually displays.

Hong Kong Japan Singapore South Korea Taiwan Thailand Vietnam Australia United States Canada Mexico United Kingdom Germany Netherlands France Italy Switzerland Poland Turkey United Arab Emirates South Africa Brazil Argentina

ROUTE LIST

Route tables by region

The table below shows representative routes from each region to illustrate how route types are distributed: Asia-Pacific has the densest concentration of dedicated lines, North America and Europe are mostly relay routes, and other regions are covered by direct routes. The full list in the client is far longer, with many more cities.

Asia-Pacific 10 sample routes

Country / Region	City	Route type	Streaming support
Hong Kong	Hong Kong	IEPL dedicated line	4K available
Japan	Tokyo	IEPL dedicated line	4K available
Japan	Osaka	Relay route	4K available
Singapore	Singapore	IEPL dedicated line	4K available
South Korea	Seoul	Relay route	4K available
Taiwan	Taipei	Relay route	4K available
Thailand	Bangkok	Direct route	1080p available
Vietnam	Ho Chi Minh City	Direct route	1080p available
Australia	Sydney	Relay route	4K available
Australia	Melbourne	Direct route	1080p available

North America 7 sample routes

Country / Region	City	Route type	Streaming support
United States	Los Angeles	IEPL dedicated line	4K available
United States	San Jose	Relay route	4K available
United States	Seattle	Relay route	4K available
United States	New York	Relay route	4K available
Canada	Toronto	Relay route	4K available
Canada	Vancouver	Direct route	1080p available
Mexico	Mexico City	Direct route	1080p available

Europe 8 sample routes

Country / Region	City	Route type	Streaming support
United Kingdom	London	IEPL dedicated line	4K available
Germany	Frankfurt	Relay route	4K available
Netherlands	Amsterdam	Relay route	4K available
France	Paris	Relay route	4K available
Italy	Milan	Direct route	1080p available
Switzerland	Zurich	Relay route	4K available
Poland	Warsaw	Direct route	1080p available
Turkey	Istanbul	Direct route	1080p available

Other regions 4 sample routes

Country / Region	City	Route type	Streaming support
United Arab Emirates	Dubai	Relay route	4K available
South Africa	Johannesburg	Direct route	1080p available
Brazil	São Paulo	Direct route	1080p available
Argentina	Buenos Aires	Direct route	1080p available

About the two columns in the table: “Route type” describes how a route forwards traffic, which determines its stability and cost at peak hours. “Streaming support” is the maximum resolution that route can reliably handle on common streaming platforms — 4K available means the route's bandwidth and egress type can sustain a 4K bitrate. The table lists only stable, static information, not latency in milliseconds or load percentages: those numbers shift with your local ISP, the time of day and even the weather, so hard-coding a value would be misleading.

LINE TYPES

Route types explained

A single city can host several routes, and the difference comes down to type. Understanding how the three types work and what they cost is more useful than memorizing city names — it decides whether you can hold a steady 4K stream at peak hours.

IEPL dedicated line

Fixed end-to-end bandwidth, no shared public egress

IEPL (International Ethernet Private Line) is a carrier-level point-to-point Layer 2 dedicated line: from entry to exit it runs on a physically isolated channel with reserved bandwidth, so it never competes with other users for the same public international egress. Its value shows most at peak hours — when the public egress congests and packet loss on ordinary routes starts to climb, the dedicated channel's available bandwidth barely changes, 4K bitrates keep running at full speed, and live streams don't drop frames the moment a match kicks off.

The trade-off is cost. Dedicated bandwidth is billed per megabit, at a unit price far above ordinary relay routes, so dedicated lines are deployed only in the cities with the highest demand: Hong Kong, Tokyo, Singapore, Los Angeles and London. These locations serve both streaming access and remote work.

Best for: 4K streaming, live sports, video calls and large file transfers.

Relay routes

Optimized path via a relay server, best value tier

A relay route works like this: you connect first to a relay server close to you, which forwards traffic along an optimized international path to the exit node. The relay server's job is to avoid congested default egress and put your traffic on a smoother link. Compared with a direct route it adds one hop, but that hop usually happens between data centers with better network quality, so the overall experience is steadier.

Cost sits between dedicated lines and direct routes, which makes relay routes the most widely deployed type: most cities in North America, Europe and Oceania run on them. They're also the workhorse for AI tools and everyday browsing — those use cases are less latency-sensitive than gaming but demand more stability than a purely direct route.

Best for: everyday browsing, AI tools, 1080p and some 4K streaming, cross-border work.

Direct routes

Straight to the exit node, lowest cost

A direct route skips the relay: the client connects straight to the exit node. It has the shortest path and the simplest setup, performs close to a relay route off-peak, and suits light users and those watching their budget. Direct routes also cover the widest range of cities — entry points in many less common regions are direct.

Its weakness is peak hours: traffic goes over the public international egress, and once that congests, both speed and stability drop. So direct routes are best used off-peak or kept as a backup — if a dedicated line goes down temporarily, switching to a direct route in the same region at least keeps you connected.

Best for: light browsing, off-peak use, backup routes, entry points in less common regions.

Route type	Forwarding	Peak-hour performance	Cost	Typical cities
IEPL dedicated line	Fixed end-to-end bandwidth on an isolated physical channel	Stable — reserved bandwidth is unaffected by public egress congestion	Highest	Hong Kong, Tokyo, Singapore, Los Angeles, London
Relay route	Nearby relay server + optimized international path	Fairly stable — the path is optimized, so congestion has limited impact	Moderate	Seoul, Taipei, Frankfurt, Paris, Sydney
Direct route	Direct connection to the exit node	Affected by public egress at peak hours; speeds drop	Lowest	Bangkok, Milan, Warsaw, São Paulo, Johannesburg

HOW TO PICK

Choosing a route by use case

A route isn't better just because it costs more — it has to match the job. Below are five common scenarios with a recommended order of selection: pick the type first, then the city, then test the routes available in that city and settle on one that stays stable for long-term use.

Everyday browsing and search

Web pages, documents and email aren't latency-sensitive and only need moderate stability. A relay route in the same region is enough: users in Asia-Pacific should favor Hong Kong, Tokyo and Singapore, while users in Europe should favor Frankfurt and Amsterdam. These tasks don't need dedicated-line capacity — leaving it for streaming and meetings actually gives you a better overall experience.

Relay route Nearby city

4K streaming and media

4K bitrates demand a sustained bandwidth supply, especially at peak hours. Prioritize IEPL dedicated lines in Hong Kong, Tokyo, Singapore, Los Angeles and London; if the platform's catalog is only available in a specific region, pick the region first and then look for a dedicated line there. When a city offers a dedicated line, don't use a direct route — that's where the streaming experience differs most.

IEPL dedicated line 4K available

AI tools

AI tools send frequent requests with small payloads, but they're sensitive to dropped connections — one interruption means starting the generation over. Choose a relay route on the US West Coast or in Japan; both sit on shorter paths to the major AI services. Don't switch routes mid-session, since that loses the context.

Relay route US / Japan

Online gaming

Games are the most latency-sensitive and need relatively little bandwidth. Pick the relay route that's geographically closest; don't connect to a node halfway around the world because the route “looks better” — no amount of route quality makes up for physical distance. In Asia-Pacific, favor Hong Kong and Tokyo, which have the most mature paths to major game servers.

Nearest relay Hong Kong / Tokyo

Remote work and file transfers

Meeting apps and code repositories need sustained, stable bandwidth rather than peak speed. Choose a dedicated line or a high-quality relay route and stick with the same one — frequent switching shows the other end different exit addresses, which can trigger security checks in some workplace systems. Schedule large file transfers for off-peak hours.

IEPL dedicated line Fixed route

FAQ

Why doesn't the route list show latency or load figures?

Latency varies with your local network, your ISP's egress, the time of day and even the weather. A static number has no reference value, and a wrong one would mislead you when choosing a route. This page lists only stable information: city, route type and streaming support. Once you subscribe, you can compare how routes actually perform inside the client — numbers measured on your own connection are the ones that mean something.

Why does one city have several routes?

A single city may offer IEPL dedicated lines, relay routes and direct routes at the same time, each serving a different purpose: dedicated lines for streaming and live events, relay routes for everyday browsing and AI tools, direct routes when budget matters most or off-peak. The client labels each by type, so the names tell them apart — you don't have to memorize which city goes with which type.

Do routes change over time?

Relay nodes and exit points are adjusted as part of routine maintenance based on carrier link quality; refresh your subscription in the client to see the latest list. Cities and route types stay stable for the life of your plan, and the route names shown in the client match the actual exit city — a route labeled Tokyo won't exit somewhere else.

What information do I need to sign up?

All you need is a username and password — no email address required. Payment supports Alipay, WeChat and USDT. Your data allowance resets every month on the day you activated, and upgrading mid-cycle converts the price difference into extra days; see the pricing page and refund policy for the exact rules.

Once you've picked a route

Monthly plans start at ¥9.9 for 60GB, ¥18 for 250GB and ¥28 for 500GB; data packs start at ¥158 for 300GB and stay valid until used up — they never expire. Every plan shares the same route list, comes with unlimited devices and a 7-day refund, no questions asked.

Try It Free View Plans

Server locations and global routes