network · coverage
VPNWI currently covers 120+ countries and 170+ routes, organized into three route types: IEPL dedicated, relay and direct. This page lists sample cities across Asia-Pacific, North America, Europe and other regions, explains the data path and best-fit use cases for each type, and shows how to choose a route by use case. No latency or load figures are listed here: real-world speed depends on your local broadband, your ISP's international gateway and the time of day, and the client shows the current status of every route.
line list
The table below lists representative cities and route types by region for easy comparison. A single country may have several routes in different data centers; the route type determines the data path, as explained in the next section.
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| Hong Kong | Hong Kong | Direct | Netflix · Disney+ |
| Singapore | Singapore | Relay | Netflix · Disney+ |
| Japan | Tokyo | IEPL dedicated line | Netflix · Prime Video |
| Japan | Osaka | Direct | Netflix · YouTube |
| South Korea | Seoul | IEPL dedicated line | Netflix · Disney+ |
| Thailand | Bangkok | Relay | YouTube · Prime Video |
| Vietnam | Ho Chi Minh City | Relay | YouTube · Prime Video |
| Malaysia | Kuala Lumpur | Relay | Netflix · Disney+ |
| Indonesia | Jakarta | Direct | Netflix · YouTube |
| Philippines | Manila | Relay | Netflix · Prime Video |
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| United States | Los Angeles | Relay | Netflix · Disney+ |
| United States | San Jose | Direct | Netflix · Hulu |
| United States | Seattle | IEPL dedicated line | Netflix · HBO Max |
| Canada | Toronto | Relay | Netflix · Prime Video |
| Mexico | Mexico City | Direct | Netflix · Disney+ |
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| United Kingdom | London | Relay | Netflix · BBC iPlayer |
| Germany | Frankfurt | IEPL dedicated line | Netflix · Prime Video |
| France | Paris | Relay | Netflix · Disney+ |
| Netherlands | Amsterdam | Relay | Netflix · Disney+ |
| Switzerland | Zurich | Direct | Netflix · Prime Video |
| Turkey | Istanbul | Relay | Netflix · YouTube |
| Country / Region | City | Route type | Streaming support |
|---|---|---|---|
| Australia | Sydney | Relay | Netflix · Disney+ |
| United Arab Emirates | Dubai | Relay | Netflix · YouTube |
| Brazil | São Paulo | Relay | Netflix · Prime Video |
| Argentina | Buenos Aires | Direct | Netflix · Disney+ |
| Egypt | Cairo | Direct | Netflix · YouTube |
The table shows a sample of cities; the full route list (170+ routes) is the subscription inside the client after you log in, and data centers and cities may change as carrier resources are adjusted.
The combination of route type and city determines two things: whether traffic takes a detour, and which region the exit IP belongs to. Start by choosing the exit region (this decides which services you can reach), then compare route types within that region (this decides how stable things are at peak hours). One subscription lets you switch between regions at any time — no need to buy twice.
line types
Route types differ not in name but in the path data takes from your device to the exit data center. The three types differ in cost and stability, and suit different uses.
An IEPL (International Ethernet Private Line) runs over a dedicated channel between the two data centers, separate from the public internet, so traffic never touches public routing and both the path and the exit bandwidth stay relatively fixed. Its value is stability: when public gateways get congested at peak hours, a dedicated line jitters less and long connections are less likely to drop. It suits continuity-sensitive uses such as 4K streaming, long video calls and cross-border work.
The trade-off is cost: it is the most expensive type, usually priced by bandwidth and line distance, so dedicated lines are generally deployed only in core regions such as Japan, South Korea and Germany. Choosing a dedicated line does not guarantee higher speed — it solves for stability, not peak throughput. For nearby regions a direct route may be faster; for distant regions a dedicated line is less likely to slow down.
Fact note: an IEPL dedicated line does not use public internet routing, so the path is fixed; actual throughput still depends on your local broadband and international gateway.
A relay route splits one connection into two legs: the client connects to the nearest entry node, which forwards traffic over an optimized backbone link to the exit node. Your side only needs to reach the closest hop, while the long intercontinental leg is handled by the backbone, so detours and packet loss are usually absorbed in the middle. It suits distant regions where a direct path would detour, such as the United States, the United Kingdom, Brazil and the UAE; relay is also common for everyday browsing and streaming.
Cost sits between dedicated and direct. One thing to note: a relay route still uses a local data center IP at the exit, so on the exit side it is no different from a direct route — streaming services and AI tools see the same exit region. Whether a relay is worth it depends on the quality of the hop from your location to the entry node, not on the name of the route.
Fact note: a relay splits the path into two legs and the client only connects to the nearest entry; the exit IP is still a local data center IP.
A direct route has the client connect straight to the exit data center with no extra entry node in between — the shortest path, the fewest forwarding hops and the simplest setup. It suits cases where your local network already has a short path to that region, such as Hong Kong, Singapore and Indonesia, and any use where you want one less hop and fewer variables.
The cheapest of the three. Direct route quality depends heavily on your ISP's gateway quality to that region: the same city can feel noticeably different on different broadband providers. When peak-hour fluctuations appear, switching to a relay or dedicated line usually improves things right away — which is why one subscription includes many routes: routes are options, not commitments.
Fact note: a direct route skips the entry node and takes the shortest path; quality depends on your ISP's gateway.
| Route type | Data path | Best for | Cost | Typical regions |
|---|---|---|---|---|
| IEPL dedicated line | Dedicated channel, no public routing | 4K streaming, video calls, cross-border work | Highest | Japan, South Korea, Germany |
| Relay | Nearest entry → backbone → exit data center | Distant regions, everyday browsing, streaming | Medium | United States, United Kingdom, Brazil, UAE |
| Direct | Client connects straight to the exit data center | Nearby regions, simplest setup | Lowest | Hong Kong, Singapore, Indonesia |
how to pick
There is no single answer to route selection: decide the use case first, then trade off distance against stability. The five scenarios below each suggest a route type to try first and how to judge it; actual results still depend on your local network.
Web pages, social apps and email are not sensitive to peak speed on a single connection, so start with the direct route closest to you — one less hop. If peak-hour fluctuations appear, switch to a relay. How to judge: connect to a direct route and a relay at the same time of day and see whether pages load consistently and whether you keep having to refresh.
4K playback is more sensitive to sustained bandwidth, so choose an IEPL dedicated line or a lightly loaded relay. Also make sure your streaming account region matches the route region: if the account is in the US, pick a US route — playing across regions triggers a region check, which usually shows up as the home page loading but playback failing.
Some AI tools require the exit IP to be in a supported region. With a relay or dedicated line, make sure the exit IP region falls within the tool's supported range; for long sessions, stay on one route rather than switching midway, so you don't have to log in again and lose context after the session drops.
Games are the most sensitive to latency and jitter, so pick the direct route with the shortest physical distance. When playing on servers in another region, try direct first, then relay, compare the two paths using the route status in the client, and lock in whichever fluctuates less instead of switching every match.
Video meetings tolerate packet loss and jitter poorly, so prefer an IEPL dedicated line: the path is fixed and steadier at peak hours. Lock in the route you use most so you don't switch mid-meeting; when teams are spread across regions, choose the exit data center nearest the participants to cut the journey in half.
coverage
Routes are grouped by region, and within each region by country and city data center. Below is an overview of the region groups currently covered; the exact countries and cities are listed in the subscription inside the client after you log in.
Covers 120+ countries / 170+ routes; one subscription works on Windows / macOS / iOS / Android / Linux with unlimited simultaneous devices, and the route each device picks does not affect the others.
faq
These four questions come up most often around route selection and using a subscription; more answers are in the Help Center.