Global Server Locations and Route Coverage
VPNTd maintains 180+ routes across 100+ countries, grouped by Asia-Pacific, North America, Europe and other regions. This page lists the key routes in each region with their types and streaming support, and explains how IEPL, relay and direct lines differ, so you can pick by use case.
Overview of Global Routes
Routes are grouped by region, and each route is labeled with its type and streaming support. The table below lists the key routes per region; the full route list is delivered to your client through the subscription link, and the in-client display is authoritative.
Asia-Pacific Routes
The closest exit direction and usually the default choice. Hong Kong and Tokyo offer IEPL dedicated lines, and Singapore covers Southeast Asia — well suited to everyday browsing and streaming.
North America Routes
For US and Canadian streaming catalogs and AI services. Los Angeles and San Jose are the workhorse exits, while New York covers East Coast services.
Europe Routes
Covering the UK, Germany, France, the Netherlands, Switzerland and Italy — good for European local services and multi-region catalogs. Frankfurt has an IEPL dedicated line.
Other Regions
Oceania, South America, Africa, the Middle East and Turkey routes for region-specific access needs; pick as needed.
| Country/Region | City | Route Type | Streaming Unlock |
|---|---|---|---|
| ASIA · Asia-Pacific Routes | |||
| Hong Kong | Hong Kong | IEPL Dedicated Line | Netflix ✓ Disney+ ✓ HBO ✓ |
| Japan | Tokyo | IEPL Dedicated Line | Netflix ✓ Disney+ ✓ HBO ✓ |
| Japan | Osaka | Relay | Netflix ✓ Disney+ ✓ HBO — |
| Singapore | Singapore | IEPL Dedicated Line | Netflix ✓ Disney+ ✓ HBO — |
| South Korea | Seoul | Relay | Netflix ✓ Disney+ ✓ HBO — |
| Thailand | Bangkok | Direct | Netflix ✓ YouTube ✓ |
| Malaysia | Kuala Lumpur | Direct | Netflix ✓ YouTube ✓ |
| NORTH AMERICA · North American Routes | |||
| United States | Los Angeles | IEPL Dedicated Line | Netflix ✓ Disney+ ✓ HBO ✓ |
| United States | San Jose | Relay | Netflix ✓ Disney+ ✓ HBO — |
| United States | Seattle | Direct | Netflix ✓ YouTube ✓ |
| United States | New York | Relay | Netflix ✓ HBO ✓ Disney+ — |
| Canada | Toronto | Direct | Netflix ✓ YouTube ✓ |
| EUROPE · European Routes | |||
| United Kingdom | London | Relay | Netflix ✓ Disney+ ✓ HBO ✓ |
| Germany | Frankfurt | IEPL Dedicated Line | Netflix ✓ Disney+ ✓ HBO — |
| Netherlands | Amsterdam | Direct | Netflix ✓ YouTube ✓ |
| France | Paris | Relay | Netflix ✓ Disney+ ✓ HBO — |
| Switzerland | Zurich | Direct | Netflix ✓ YouTube ✓ |
| Italy | Milan | Direct | Netflix ✓ Disney+ ✓ HBO — |
| OTHERS · Other Regions | |||
| Australia | Sydney | Direct | Netflix ✓ YouTube ✓ |
| New Zealand | Auckland | Direct | Netflix ✓ Disney+ — |
| Brazil | São Paulo | Relay | Netflix ✓ Disney+ — |
| South Africa | Johannesburg | Relay | Netflix ✓ Disney+ — |
| Turkey | Istanbul | Direct | Netflix ✓ Disney+ — |
| United Arab Emirates | Dubai | Direct | Netflix ✓ Disney+ — |
Route Types Explained: IEPL / Relay / Direct
The three route types differ in transmission path and cost structure. Once you understand the differences, picking by use case works far better than blind-picking by region.
IEPL Dedicated Line
How it works: IEPL (International Ethernet Private Line) is a point-to-point dedicated link that never touches the public internet between entry and exit. Data travels entirely inside the private line, unaffected by congestion on the cross-border public segment, keeping packet loss and jitter very low.
Best for: rock-steady connections during evening peak hours, 4K streaming, live broadcasts, long-lived AI tool sessions with streaming output, and loss-sensitive real-time applications.
Cost & deployment: priced by bandwidth, IEPL is the most expensive of the three types, so it is deployed only on core directions such as Hong Kong, Tokyo, Singapore, Los Angeles and Frankfurt.
Relay Routes
How it works: a relay route first connects to a relay server, which then forwards traffic to the landing data center. The relay segment is optimized for cross-border paths, easing the packet loss and jitter of direct public-internet transit — noticeably more stable than a direct connection.
Best for: everyday browsing, remote work, standard-definition streaming, and directions without IEPL coverage. The best value pick for most situations.
Cost & deployment: costs sit between IEPL and direct, deployment is flexible, and it covers more countries than either of the other types.
Direct Routes
How it works: a direct route connects straight from your client to the landing data center with no relay in between. The path is shortest with minimal overhead; real-world performance depends on the public internet quality between the two ends.
Best for: off-peak hours and directions with good network quality, bulk downloads, and cases where the landing IP needs to serve connections directly.
Cost & deployment: the cheapest of the three, usually stable off-peak; the cross-border public segment may congest at peak times, when switching to IEPL or relay is recommended.
Choosing Routes by Use Case
The same route can behave very differently depending on the use case. Below are route-type and region suggestions for common use cases — your in-client experience is the final word.
Everyday Browsing
Pick the physically closest Asia-Pacific routes — Hong Kong, Tokyo or Singapore all work, whether relay or IEPL. For plain web browsing and instant messaging, direct routes are usually enough too; switching costs little, so try a few before settling on one.
Movies & Streaming
Netflix, Disney+ and similar services determine your region by exit IP, so pick a route in the region whose catalog you want to watch. 4K bitrates demand bandwidth and stability — go with IEPL first to avoid peak-hour bitrate dips degrading picture quality.
AI Tools
AI services like ChatGPT are far more sensitive to exit IP and connection stability than ordinary websites; long-lived sessions and streaming output break easily under jitter. Stick to one IEPL route and avoid frequent exit-IP changes that can trip risk controls.
Online Gaming
Games are the most sensitive to latency and packet loss, so pick physically close routes: Hong Kong, Tokyo or Singapore for Asian servers, Los Angeles or San Jose for US servers. Avoid direct routes during gaming hours — prefer IEPL or relay.
Remote Work
Video calls and large file syncs need stable uplink and downlink. Use IEPL or relay routes and stick to one route to avoid mid-meeting reconnects from switching exits. A direct route can serve as a backup during office hours.
Downloads & Updates
Bulk downloads don't care much about latency — spare bandwidth matters more. Off-peak, direct routes are usually stable and cheapest; at peak times, move heavy download jobs to IEPL to avoid stacking on public-internet congestion.
Subscription Delivery and Route Updates
Routes don't need manual, one-by-one configuration. Your client fetches the full route list via a subscription link, including route names, regions and type labels. Grab the link from the user panel, import it into your client, and every route appears in the list.
When new routes come online or existing ones change, just update the subscription in your client to sync the latest list — no reinstall or manual edits needed. You can filter routes by region and type in the client, and switching takes effect immediately without a restart.
The tables on this page list the key routes per region. The full list — 100+ countries / 180+ routes, growing as new routes come online — is what you'll see in the client.
Route FAQ
My client shows more routes than this page's tables — which one is right?
How do I tell route types apart in the client?
Which route type should I pick during evening peak?
100+ countries / 180+ routes, subscriptions from ¥9.9/month, unlimited simultaneous devices, military-grade encryption, 60-day money-back guarantee. No email address needed — register with just a username and password. Alipay / WeChat Pay / USDT accepted.