Global nodes and route coverage
VPNVL currently covers 120+ countries / 180+ routes. The table below lists a sample of commonly used routes by Asia-Pacific, North America, Europe and other regions, with route type and streaming support noted. Route type decides how steady and how fast a connection feels at peak hours, so read the three route types below before you pick one.
Asia-Pacific routes
Asia-Pacific is the shortest path when you reach international sites. The Hong Kong, Tokyo and Singapore IEPL routes travel on carrier dedicated lines, so the international leg never crosses the public internet and stays steady through the 8–11 pm weekday congestion window. Osaka and Kuala Lumpur are relay routes: traffic enters at the nearest entry point and is forwarded to the exit node, which costs one tier less than a dedicated line and suits cases where the exit city is fixed but the budget is tight. Seoul, Ho Chi Minh City and Jakarta are direct — shortest path, fewest hops, best for users whose local network is already solid. The Mumbai route mainly serves South Asian platforms and some developer services; round-trip time is longer than on East Asian routes, so skip it unless you need it.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Hong Kong | Hong Kong | IEPL dedicated | Yes |
| Japan | Tokyo | IEPL dedicated | Yes |
| Japan | Osaka | Relay | Yes |
| Singapore | Singapore | IEPL dedicated | Yes |
| South Korea | Seoul | Direct | Yes |
| Malaysia | Kuala Lumpur | Relay | Partial |
| Thailand | Bangkok | Relay | Partial |
| Vietnam | Ho Chi Minh City | Direct | Partial |
| Indonesia | Jakarta | Direct | Partial |
| India | Mumbai | Relay | Partial |
North America routes
North American routes cover three needs: long AI tool sessions, developer documentation and code hosting, and US streaming. Los Angeles is an IEPL dedicated route and the main North American exit for this service; San Jose is direct, a good fit for services hosted in California; Seattle and New York are relay routes, which save one public-internet detour compared with direct when you reach East Coast resources from the West. Toronto and Mexico City round out local exits for Canada and Mexico, which works better for local banks, government sites and local streaming. The physical distance across the Pacific means North American round-trip times are higher than Asia-Pacific ones: keep everyday browsing on Asia-Pacific and switch only when you specifically need a North American exit.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United States | Los Angeles | IEPL dedicated | Yes |
| United States | San Jose | Direct | Yes |
| United States | Seattle | Relay | Yes |
| United States | New York | Relay | Yes |
| Canada | Toronto | Direct | Yes |
| Mexico | Mexico City | Direct | Partial |
Europe routes
European routes sit in the cities with the densest traffic exchange. London and Zurich are IEPL dedicated; Frankfurt and Amsterdam are relay routes — both are major European internet exchange points, so exits to neighbouring countries stay consistent; Paris, Stockholm, Madrid and Warsaw are direct, added for coverage. European routes are typically used for European streaming catalogues, EU-only services, and developer tools that deploy nodes only in Europe. Note that round-trip times to Europe are naturally higher than to Asia-Pacific, so unless the target service only offers an entry point in Europe, there is no need to make it your default.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United Kingdom | London | IEPL dedicated | Yes |
| Germany | Frankfurt | Relay | Yes |
| Netherlands | Amsterdam | Relay | Yes |
| France | Paris | Direct | Yes |
| Switzerland | Zurich | IEPL dedicated | Yes |
| Sweden | Stockholm | Direct | Partial |
| Spain | Madrid | Direct | Partial |
| Italy | Milan | Relay | Partial |
| Poland | Warsaw | Direct | Partial |
Other regions
Australia, New Zealand, the UAE, Brazil and South Africa complete coverage for the southern hemisphere, the Middle East and South America. These regions are far from mainland China and the round trip is long, so use them only when you need local services — local streaming, local e-commerce, local banks and government sites; keep everyday browsing on Asia-Pacific routes. Sydney is IEPL dedicated, Melbourne and Dubai are relay, and Auckland, São Paulo and Johannesburg are direct. If you only drop in occasionally, a relay route is enough — there is no need to pin a node for a single scenario.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Australia | Sydney | IEPL dedicated | Yes |
| Australia | Melbourne | Relay | Yes |
| New Zealand | Auckland | Direct | Partial |
| United Arab Emirates | Dubai | Relay | Partial |
| Brazil | São Paulo | Direct | Partial |
| South Africa | Johannesburg | Direct | Partial |
Three route types
Every route label in the table maps to one network structure. The difference is not about “fast or slow” but about how the international leg travels, how steady it stays at peak hours, and where the cost sits. One city can host several types at once; the client separates them by label, so check the label before the city name when you switch.
IEPL dedicated
Dedicated line out; the international leg never shares the public internet
- How it works
- A carrier-provided international dedicated line. Data travels from the local entry point over the dedicated line straight to the overseas exit; the international leg never crosses the public internet and never competes for bandwidth with other users.
- Best for
- Long-lived connections that must stay steady at peak hours and are sensitive to packet loss: continuous AI tool sessions, video meetings, large uploads and downloads.
- Cost
- The highest cost per unit of bandwidth, so these are deployed only in the busiest cities; every dedicated route in the table belongs to this class.
Relay
Nearest entry point, then forwarded to the exit
- How it works
- The client connects to the nearest relay entry point, and the relay server forwards traffic to the exit node. The international leg takes an optimised path; the exit leg then joins the public internet.
- Best for
- Cases where direct quality is average but the exit city is fixed; steadier than direct at peak hours, at the cost of one extra hop.
- Cost
- Medium — cheaper than dedicated, pricier than direct. It is the compromise between coverage and cost, and the default choice in most regions.
Direct
Shortest path, fewest hops
- How it works
- The client connects straight to the exit server with no relay in between: shortest path, fewest hops, and no extra relay bandwidth consumed.
- Best for
- Good local network quality and a target service near the exit city; also commonly used to fill in coverage.
- Cost
- The lowest, so direct routes carry coverage rather than the main load — a good fit for occasional access to a region.
Choosing a route by use case
No route is universally better; what matters is whether it matches your scenario. Below are recommendations for six common use cases, each mapped to the route types in the table above, so you can filter by label in the client.
Everyday browsing
01For international sites, research and documentation, start with the IEPL dedicated routes in Hong Kong or Tokyo: shorter physical distance and a shorter round trip make first paint feel closest to a local site. If a dedicated route queues up at certain hours, switch to a relay route in the same region — the exit city stays the same, and neither your login state nor the page language changes.
Streaming
02Routes marked “Supported” in the table have been tuned for streaming, with separate exits for the US, Japan, UK and Australia catalogues. 4K playback depends more on steady bandwidth than on peak speed, so pin one dedicated or relay route and avoid switching nodes mid-playback — a switch makes the player renegotiate and buffer for a few seconds.
AI Tools
03AI tool requests are long-lived: one conversation can run from tens of seconds to several minutes, and a dropped stream shows up as a cut-off answer or a resend. Prefer IEPL dedicated here, then relay; don't switch routes mid-conversation. If responses slow down, first check whether a single service is slow before changing routes.
Gaming
04Games are the most sensitive to round-trip time and need little bandwidth. Pick the route with the shortest physical distance: Hong Kong for southern China, Tokyo or Osaka for eastern China, Seoul for northern China. Dedicated first, direct second; a relay adds a hop and usually lengthens the round trip, so only switch when direct shows obvious packet loss.
Work and collaboration
05Video meetings, enterprise cloud-drive sync and cross-border collaboration tools are all long, steady connections. For meetings, use a dedicated route and pin it — don't enable auto-switching, because auto-switch changes the exit when the network jitters and the meeting client has to re-handshake. File sync jobs can run on relay routes at lower cost.
Multiple devices at once
06One account covers unlimited devices, and phone, laptop and tablet can each pick a different route: phone on an Asia-Pacific dedicated route for video, laptop on a North American dedicated route for AI tools, with no effect on each other. Data is shared across all devices and resets monthly on your activation date; when several devices are online at once, put the heaviest bandwidth task on a dedicated route.
Coverage and plans
120+ countries / 180+ routes is the current overall coverage. The table above lists a sample of commonly used routes; the full list expands by region inside the client. Every monthly plan can use all routes with no device limit, and one data allowance is shared across all your devices.
Monthly plans: ¥9.9/month for 60GB, ¥18/month for 250GB, ¥28/month for 500GB. Data resets each month on your activation date, and mid-cycle upgrades are prorated for the remaining days. If you go over your plan in a month, you can stack data packs (use them up whenever — they never expire): ¥158/300GB, ¥358/1000GB, ¥658/3000GB.
There is no single right answer: in the same city, different ISPs can take different paths to the same exit node. Run the default recommended route for a day, then fine-tune for the scenarios above; the 60-day money-back guarantee covers your first payment, so you can compare routes with confidence during that window.