ROUTE INDEX · Server Locations
Server Locations and Global Routes
This page is VPNWY's route index: it lists representative routes for four regions (Asia Pacific, North America, Europe and other), explains how IEPL dedicated, relay and direct routes differ, and offers advice on choosing by use case. Together the routes cover 110+ countries / 150+ routes, and one subscription works on unlimited devices.
The full route list lives in the client's Routes window: sign in and fetch your subscription to see the nodes currently available, grouped by region and switchable in one click — no manual node addresses to maintain.
- 110+ countries / 150+ routes
- Unlimited devices
- 30-day refund, no questions asked
- No email address required
- Quantum encryption
Asia Pacific Routes
The Asia Pacific group has the shortest geographic distance and the shortest round trip, making it the first choice for everyday access, video playback and AI tool sessions. Hong Kong nodes run on IEPL dedicated lines, Japan and South Korea are mostly relay, and Singapore plus the Southeast and South Asian cities are direct.
The table below lists representative routes in the Asia Pacific group; the full list is shown grouped by region in the client's Routes window.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Hong Kong | Hong Kong | IEPL Dedicated | Netflix · Disney+ · YouTube |
| Japan | Tokyo | Relay | Netflix · Disney+ · Abema |
| Japan | Osaka | Direct | Netflix · YouTube |
| Singapore | Singapore | Direct | Netflix · Disney+ · YouTube |
| South Korea | Seoul | Relay | Netflix · Wavve |
| Malaysia | Kuala Lumpur | Direct | Netflix |
| Thailand | Bangkok | Direct | Netflix |
| Vietnam | Ho Chi Minh City | Direct | Netflix |
| Indonesia | Jakarta | Direct | Netflix |
| India | Mumbai | Direct | Netflix · Prime Video |
| Australia | Sydney | Relay | Netflix · Stan |
| New Zealand | Auckland | Direct | Netflix |
North America Routes
North American routes mainly serve US content libraries and US service accounts: Los Angeles and New York are relay, the other cities are direct. US streaming, app stores and gaming platforms all have a matching exit location in this group.
US routes are mostly direct, while the relay nodes in Los Angeles and New York suit long sessions during peak evening hours.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United States | Los Angeles | Relay | Netflix · Disney+ · Hulu |
| United States | San Jose | Direct | Netflix · Hulu |
| United States | Seattle | Direct | Netflix · HBO Max |
| United States | Dallas | Direct | Netflix · Hulu |
| United States | New York | Relay | Netflix · Disney+ · HBO Max |
| Canada | Toronto | Relay | Netflix · Crave |
| Canada | Vancouver | Direct | Netflix |
| Mexico | Mexico City | Direct | Netflix |
Europe Routes
European routes cover the main data center cities of Western and Northern Europe, with London and Frankfurt as relay and the rest as direct. UK, German and French content libraries and local services map to their respective countries' exit locations.
European cities are mostly direct, while the relay nodes in London and Frankfurt carry intercontinental traffic.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United Kingdom | London | Relay | Netflix · BBC iPlayer |
| Germany | Frankfurt | Relay | Netflix · Disney+ |
| France | Paris | Direct | Netflix · Canal+ |
| Netherlands | Amsterdam | Direct | Netflix |
| Italy | Milan | Direct | Netflix · RaiPlay |
| Spain | Madrid | Direct | Netflix |
| Sweden | Stockholm | Direct | Netflix |
| Poland | Warsaw | Direct | Netflix |
| Ireland | Dublin | Direct | Netflix |
Routes in Other Regions
Routes in the Middle East, South America and Africa are for reaching local content libraries and localized services. This group is mostly direct, with Dubai as relay, and suits specific cases that need an exit IP in the matching country.
This group has fewer routes than the first three; it exists to fill in country and region exit locations.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United Arab Emirates | Dubai | Relay | Netflix |
| Turkey | Istanbul | Direct | Netflix |
| Israel | Tel Aviv | Direct | Netflix |
| Brazil | São Paulo | Direct | Netflix |
| Argentina | Buenos Aires | Direct | Netflix |
| South Africa | Johannesburg | Direct | Netflix |
The Streaming column shows the content libraries commonly reachable from that route's exit location; what you can actually watch is decided by each platform's own regional policy and changes over time.
Route Types: IEPL Dedicated, Relay and Direct
The difference between the three types comes down to how many hops a packet takes from entry to exit, and who guarantees that path. Each type differs in stability, best use case and cost; all three work within the same subscription.
IEPL Dedicated
How it works: a point-to-point dedicated line runs from the entry data center to the exit data center, so packets skip the intermediate nodes of the public internet and the path stays fixed.
- Best for long video playback during peak hours, long AI tool sessions, and work connections that need to stay online.
- Cost the highest cost per unit of bandwidth of the three types, so it is deployed mainly in core locations such as Hong Kong.
Relay
How it works: the entry node aggregates traffic first, then sends it over an optimized relay link to the exit data center. That is one hop more than a direct route, but the hop runs on a carrier-optimized path that avoids the congested routes of the public internet.
- Best for distant regions where direct connections tend to fluctuate, such as Japan, South Korea and the US West Coast; usually more stable than direct routes during peak hours.
- Cost mid-range, and the main type covering core regions.
Direct
How it works: the client connects straight to the node in the exit data center — the shortest path with the fewest hops, and an exit IP located in the city you chose.
- Best for cases that need an exit IP in a specific country: local content libraries, signing up for and logging into local services, and everyday browsing from a nearby city.
- Cost the lowest, which is why it covers the most cities and countries.
Cost differences never show up in the subscription price: all three route types work with the same subscription, and price and traffic are counted by plan only (¥9.9/month for 60GB, ¥18/month for 250GB, ¥28/month for 500GB).
Choose Routes by Use Case
No route is inherently better than another — what matters is whether it fits what you are doing. Below are the picking orders for five common scenarios; switching routes in the client takes one click.
Everyday browsing and research
Web pages, documents and dashboards don't need much bandwidth, but they are sensitive to response time. Start with the nearest region — Hong Kong, Japan, Singapore; when a city has several routes, try each one and settle on the most stable.
4K streaming and binge-watching
Streaming comes down to two things: sustained bandwidth across a full session, and the country the exit IP belongs to. The country decides which content library you can reach, the route decides whether playback stays smooth — for US, UK and Japan libraries, pick a route in the matching country.
AI tools and long sessions
AI tools mostly run on long-lived sessions, and a mid-session drop loses the context. For these, prefer a dedicated line or relay with a fixed path, and pin your usual region to one route to avoid reconnects from constant switching.
Gaming and real-time matches
Games are more sensitive to jitter than to bandwidth — one dropped packet is one rubber-band. Choose a dedicated line or relay with a fixed path, and prefer a node in the same region as the game server; intercontinental routes fluctuate more during peak hours.
Remote work and file transfers
Work scenarios need both upload and download: video calls depend on download stability, file sync on upload. Relay routes are better balanced under mixed load; if your city has a direct node, keep it as a backup.
Coverage by Region
Together the routes cover 110+ countries / 150+ routes. Major cities are listed by region below; the client's route window is the authoritative full list.
Asia Pacific
Hong Kong runs on an IEPL dedicated line, Tokyo, Seoul and Sydney are relay, and the remaining cities are direct.
- Hong Kong
- Japan
- Singapore
- South Korea
- Malaysia
- Thailand
- Vietnam
- Indonesia
- India
- Australia
- New Zealand
North America
Los Angeles and New York are relay, the other US and Canadian cities are direct; Mexico City covers Latin American content libraries.
- United States
- Canada
- Mexico
Europe
London and Frankfurt are relay, the other cities are direct; UK, German and French content libraries map to their respective countries.
- United Kingdom
- Germany
- France
- Netherlands
- Italy
- Spain
- Sweden
- Poland
- Ireland
Other regions
Dubai is relay, the other cities are direct; useful for specific cases that need an exit IP in the matching country.
- United Arab Emirates
- Turkey
- Israel
- Brazil
- Argentina
- South Africa
Route FAQ
Questions about picking by use case, by region and by route type are collected here.
How should I choose between IEPL dedicated, relay and direct routes?
Start with the use case: for video, gaming and long sessions, prefer a dedicated line or relay; when you need an exit IP in a specific country, use direct. If you're unsure, start with the nearest region, use a few routes for a while each, and keep the most stable one. All three types work within the same subscription, and switching costs nothing extra.
Why does the same city show up with several routes?
One city can have dedicated, relay and direct routes at the same time; they differ in entry point, path and exit data center, and suit different uses. The client groups them by region, so repeated city names mean different route types.
Does the route list change?
Yes. New data centers, route maintenance and carrier routing changes all alter the list. The client updates automatically through the subscription link, so there is no need to re-import anything by hand; if a route is temporarily unavailable, switch to another route in the same region.
How many devices can use one subscription at the same time?
Unlimited. Windows, macOS, iOS, Android and Linux share the same subscription, and each device can pick a different route without affecting the others.
Does the route type affect whether streaming works?
Not much. What decides the content library is the country the exit IP belongs to, not the route type; dedicated and direct routes in the same country see the same libraries. Whether playback stays smooth depends on how the route performs across the whole session.
Is there any link between routes and plan pricing?
No. All three route types work with the same subscription, and the price depends only on plan traffic: ¥9.9/month for 60GB, ¥18/month for 250GB, ¥28/month for 500GB; traffic packs are ¥158/300GB, ¥358/1000GB and ¥658/3000GB, valid until used up and never expiring. A 30-day refund is available.