Nodes / Route List
110+ countries / 160+ routes, with no limit on simultaneous devices, on Windows / macOS / iOS / Android / Linux. The table below is grouped into Asia Pacific, North America, Europe and other regions, with route type and streaming support noted for each entry, so you can pick an exit by use case.
01 / Regions
One thing to get straight about the table: route types come in just three kinds — IEPL dedicated, relay and direct — and the next section explains how each works and where it fits. The table does not list latency in milliseconds: latency moves with your local broadband, your ISP's exit and the time of day, and the same route can be twice as fast in the morning as it is at peak hours, so a fixed number would mislead more than it helps. Judge a route by three things — route type, exit region and streaming support — and weigh them against what you actually need.
All routes share one subscription: switching exit regions needs no re-import of the config and costs nothing extra; simultaneous devices are unlimited, so your laptop, desktop and tablet can each connect to a different exit.
Asia Pacific is the busiest region: Hong Kong, Singapore, Tokyo and Seoul handle most day-to-day cross-border access, and Hong Kong and Tokyo run on IEPL dedicated lines — the first choice for Japanese and Korean streaming.
| Country / Region | City | Route Type | Streaming and Common Services |
|---|---|---|---|
| Hong Kong | Hong Kong | IEPL Dedicated | Netflix / Disney+ / HBO Max |
| Singapore | Singapore | IEPL Dedicated | Netflix / Disney+ / YouTube 4K |
| Japan | Tokyo | IEPL Dedicated | Netflix / ABEMA / dアニメ |
| Japan | Osaka | Relay | Netflix / ABEMA |
| South Korea | Seoul | Relay | Netflix / Wavve |
| Malaysia | Kuala Lumpur | Relay | Netflix / Disney+ |
| Thailand | Bangkok | Relay | Netflix / Disney+ |
| Vietnam | Ho Chi Minh City | Direct | Netflix |
| Indonesia | Jakarta | Direct | Netflix / Disney+ |
| Philippines | Manila | Direct | Netflix |
| India | Mumbai | Relay | Netflix / Prime Video |
| Australia | Sydney | Relay | Netflix / Stan |
North America covers both coasts with Los Angeles, San Jose and New York: AI tools and US streaming mostly run through this region, and Los Angeles is an IEPL dedicated line, well suited to long, continuous sessions.
| Country / Region | City | Route Type | Streaming and Common Services |
|---|---|---|---|
| United States | Los Angeles | IEPL Dedicated | Netflix / Disney+ / HBO Max / AI Tools |
| United States | San Jose | Relay | Netflix / Disney+ / AI Tools |
| United States | New York | Relay | Netflix / HBO Max |
| Canada | Toronto | Relay | Netflix / Crave |
Europe covers the UK, Germany, France, the Netherlands, Italy, Spain, Sweden and Turkey: a good fit for European streaming, European sites and cross-time-zone collaboration, with London on an IEPL dedicated line.
| Country / Region | City | Route Type | Streaming and Common Services |
|---|---|---|---|
| United Kingdom | London | IEPL Dedicated | Netflix / BBC iPlayer |
| Germany | Frankfurt | Relay | Netflix / Disney+ |
| France | Paris | Relay | Netflix / Canal+ |
| Netherlands | Amsterdam | Relay | Netflix / Disney+ |
| Italy | Milan | Relay | Netflix / RaiPlay |
| Spain | Madrid | Direct | Netflix / Movistar+ |
| Sweden | Stockholm | Direct | Netflix / SVT Play |
| Turkey | Istanbul | Direct | Netflix |
The other regions cover the Middle East, South America, Africa and Latin America: useful for local sites, working with local teams, or as backup exits on long-haul routes; Dubai runs on a relay route.
| Country / Region | City | Route Type | Streaming and Common Services |
|---|---|---|---|
| United Arab Emirates | Dubai | Relay | Netflix / OSN+ |
| Brazil | São Paulo | Direct | Netflix / Globoplay |
| South Africa | Johannesburg | Direct | Netflix |
| Mexico | Mexico City | Direct | Netflix / Disney+ |
02 / Line Types
IEPL stands for International Ethernet Private Line. The carrier carves out an exclusive Ethernet channel between two endpoints, so traffic enters the private line at the local access point and never passes through public internet exit nodes. What users feel most directly: at peak hours the speed curve stays almost as flat as during the day — no more smooth daytime browsing that collapses to a few dozen KB/s at night.
Dedicated capacity is bought outright, so fewer people share it at any one moment, and packet loss and jitter are noticeably lower than on public links. The trade-off is that dedicated lines are billed by bandwidth, making them the most expensive of the three types per unit, so they are deployed only at the busiest core exits: Hong Kong, Tokyo, Los Angeles and London.
A relay route adds one hop between your local entry point and the target exit: traffic first reaches a relay node, which then uses a better-quality exit to reach the target site. That is one hop more than a direct route, but it bypasses congested public exits, so real-world performance is usually steadier than direct.
When choosing a relay route, what matters is not the hop count but whether the segment between the relay node and the exit is congested. VPNBQ applies exit selection at relay nodes: each city keeps several backup exits, and when one becomes congested traffic switches to a backup automatically — nothing to do on your end.
A direct route skips the relay: traffic lands at the exit data center and reaches the target site from there. It is the shortest path and the simplest setup, and the easiest to troubleshoot when something goes wrong. It also has the widest coverage — the cities on the route list that only local users would visit are almost all direct.
The weak spot of direct routes is peak hours: exit bandwidth rides on public links, so evening fluctuations are more visible than on dedicated or relay routes. That is why VPNBQ positions direct routes as coverage plus backup: use them when you need a local native IP, and they take over when a primary route is under maintenance.
03 / Selection
There is a simple three-step order to picking a route: first choose the route type by use case, then pick the exit city by where the target service lives, and finally add one backup route in the same region. With two routes in a region, you can switch straight over when one is under maintenance — no subscription changes, no re-importing configs.
| Use Case | Preferred Route Type | Region Order | Notes |
|---|---|---|---|
| Everyday browsing and research | Relay | Hong Kong → Singapore → Tokyo | Short paths and fast switching keep time to first byte steady |
| Streaming video | IEPL Dedicated | Hong Kong / Tokyo → Los Angeles → London | Long playback sessions are more sensitive to packet loss — prefer dedicated lines |
| AI tools | IEPL Dedicated / Relay | Los Angeles → San Jose → Tokyo | Long chats and long-form generation can't afford a mid-stream drop |
| Online gaming | Relay | Hong Kong / Tokyo / Seoul (nearest) | Pick the physically closest exit to cut round-trip hops |
| Cross-time-zone work | IEPL Dedicated | Choose by where your collaborators are | Video calls and file sync depend on stable upload |
Web requests are many and small: bandwidth hardly matters, but time to first byte does. A relay route through Hong Kong or Singapore makes pages open with almost no wait; when you need local material from a specific region, switch to the direct route in that city.
Over a 45-minute episode, a single noticeable packet loss turns into a spinning buffer wheel. Prefer IEPL dedicated lines: Hong Kong and Tokyo serve Japanese and Korean content, while US content goes through Los Angeles. Before you hit play, make sure your account region matches the exit region so the platform's region checks don't keep firing.
Long chats, long-form generation and file uploads are sustained connections, and a mid-stream drop loses the whole session context. Keep one Los Angeles dedicated line as your primary and the San Jose relay as backup; avoid hopping the same account between regions too often.
Games care about both absolute latency and jitter, so the first rule is physical proximity: players in Asia should start with Hong Kong, Tokyo and Seoul. Exit selection on relay routes cuts detours and is steadier than direct; cross-continent play is limited by distance itself, and no route can remove the round-trip time.
Video calls, code repo sync and cloud document collaboration are all two-way traffic, where upload stability matters more than download. Choose the exit by where your team is: London or Frankfurt for European teams, Los Angeles or New York for North American teams, Hong Kong or Tokyo for Asian teams.
When travelling or briefly needing a local service in some region, don't overthink the route type — just pick a direct route by city. What is worth preparing in advance is a backup: keep at least one more route in the same region as your primary city, and switching is just picking another exit in the client.
04 / Coverage
110+ countries / 160+ routes is the current coverage on sale. Every region keeps at least one primary and one backup route, and specific cities shift with carrier resources and local network conditions: new cities are added to your existing subscription, retired cities are removed from the route list in advance, and the rest of your subscription is unaffected.
All routes share one subscription, with no limit on simultaneous devices, and one account works across Windows / macOS / iOS / Android / Linux. Payment supports Alipay / WeChat / USDT; no email address is needed to sign up — just a username and password. 14-day refund, no questions asked.
05 / FAQ
Latency moves with your local broadband, your ISP's exit and the time of day, and the same route can differ by more than double across networks. A fixed number would be read as a promise and cause more confusion than clarity. The list keeps only three facts you can verify over time: exit region, route type and streaming support — the real speed is best measured on your own connection.
Your subscription covers every region on the route list; switching exits needs no re-import and costs nothing extra. Simultaneous devices are unlimited, so your phone, computer and tablet can each connect to a different exit without affecting one another.
Go by use case: for sessions that can't drop mid-way — long playback, long AI chats, cross-time-zone video calls — prefer a dedicated line; for web browsing, standard streaming and file transfers, a relay is plenty. Both types share one subscription, so you can switch and compare anytime.
The label means that exit region has the platform's regional catalog; whether you can actually play it also depends on your account region and the platform's licensing rules. Before you start, check that your account region matches the exit region so the platform's region checks don't keep firing.
Retired cities are removed from the route list in advance; the rest of your subscription is unaffected and no re-import is needed. Every region keeps at least one primary and one backup route, so when a single route is under maintenance, just switch to another one in the same region.
Monthly plan data resets each month on your activation date, and if you upgrade mid-cycle the price difference is prorated over the remaining days. Data packs last until used up and never expire, which suits users with irregular usage. All routes share one subscription, and switching exits doesn't use extra data.
Next step: once you've picked a route, import the subscription for your platform on the Guides page; plan prices and data pack sizes are on the Pricing page. Every plan includes a 14-day refund, no questions asked, and no email address is needed to sign up.