Asia Pacific routes
Asia Pacific is the busiest group. Hong Kong and Tokyo are dedicated routes with fixed paths and little jitter at peak hours, which suits long sessions and video calls. Osaka, Seoul and Bangkok are relay routes — a compromise between price and stability. Taipei, Kuala Lumpur, Ho Chi Minh City and Mumbai are direct routes: shortest path, lowest cost, good for web browsing and looking things up. When you want Hong Kong or Japan streaming, switch routes within the same region rather than jumping to a distant one — crossing regions often fixes speed while creating a new region-detection problem.
Main Asia Pacific routes
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Hong Kong | Hong Kong | Dedicated | Netflix / Disney+ |
| Japan | Tokyo | Dedicated | Netflix / Disney+ / Hulu |
| Japan | Osaka | Relay | YouTube Premium |
| Singapore | Singapore | Dedicated | Netflix / Disney+ |
| South Korea | Seoul | Relay | Netflix |
| Taiwan | Taipei | Direct | Netflix |
| Malaysia | Kuala Lumpur | Direct | — |
| Thailand | Bangkok | Relay | Netflix |
| Vietnam | Ho Chi Minh City | Direct | — |
| India | Mumbai | Direct | Prime Video |
North America routes
North American routes mainly serve streaming and AI tools. Los Angeles and San Jose are the two shortest trans-Pacific landing points, so first frames load faster for US content; New York is better for East Coast work and collaboration services. Toronto, Vancouver and Mexico City are direct routes, useful for local sites and checking regional prices. If an AI tool drops mid-generation, switch to another relay in the same region first, then consider another region — changing continents usually just makes long connections less stable.
Main North America routes
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United States | Los Angeles | Dedicated | Netflix / Disney+ / HBO Max |
| United States | San Jose | Relay | Netflix / Hulu |
| United States | New York | Relay | Netflix / Prime Video |
| Canada | Toronto | Direct | Netflix |
| Canada | Vancouver | Direct | Netflix / Disney+ |
| Mexico | Mexico City | Direct | Netflix |
Europe routes
Europe covers nine countries: the UK, Germany, France, the Netherlands, Spain, Italy, Sweden, Switzerland and Turkey. London and Frankfurt are dedicated routes, suited to services like BBC iPlayer that are sensitive to both region and route quality; Paris, Amsterdam and Zurich are relay routes; Madrid, Milan, Stockholm and Istanbul are direct. Cross-region access between Europe and Asia Pacific is inherently higher-latency, so avoid cross-region viewing unless you need it; if you do need European content, sort out the account region and payment region first, then look at routes.
Main Europe routes
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United Kingdom | London | Dedicated | BBC iPlayer / Netflix |
| Germany | Frankfurt | Dedicated | Netflix / Disney+ |
| France | Paris | Relay | Netflix |
| Netherlands | Amsterdam | Relay | Netflix / Disney+ |
| Spain | Madrid | Direct | Netflix |
| Italy | Milan | Direct | Netflix / Prime Video |
| Sweden | Stockholm | Direct | Netflix |
| Switzerland | Zurich | Relay | Netflix |
| Turkey | Istanbul | Direct | — |
Routes in other regions
Other regions cover Oceania, the Middle East, South America and Africa. Sydney, Auckland, São Paulo, Cairo and Buenos Aires are direct routes; Dubai is a relay. These regions have fewer routes than Asia Pacific and Europe and are mainly for local sites, checking regional prices, or working with local teams. Before using a cross-region route, confirm one thing: does the target service really decide content by exit region? If it goes by account region or payment region, switching routes will not change the result.
Oceania / Middle East / South America / Africa
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Australia | Sydney | Direct | Netflix / Disney+ |
| New Zealand | Auckland | Direct | Netflix |
| United Arab Emirates | Dubai | Relay | Netflix |
| Brazil | São Paulo | Direct | Netflix |
| Egypt | Cairo | Direct | Netflix |
| Argentina | Buenos Aires | Direct | Netflix |
The table shows a sample of commonly used routes to illustrate regional coverage and route types; it is not the total. The 150+ routes at the top of the page is the total number the service currently offers, and the full list expands by region inside the client. The streaming column names the platforms a route is commonly used for; platform policies change, so what actually opens is what counts. Routes marked “—” are mainly for general web and work access.
Three route types
The three route types do not differ in “fast or slow” but in who guarantees the path, who schedules traffic when it congests, and what a unit of bandwidth costs. Look at those three things separately and you no longer have to pick routes by trial and error. The notes below match the three labels in the route type column.
IEPL dedicated line
An end-to-end Ethernet dedicated line: traffic between the two ends travels a fixed carrier-level channel, and the international leg never touches congested public exits. Data follows the same guaranteed path from entry to exit, so jitter and packet loss are both lower.
- Best for: peak-hour live streams, video calls, long large-file transfers
- Best for: AI tool sessions that need to stay connected
- Cost: highest per unit of bandwidth; capacity goes to the busiest regions first
Relay route
You connect to a relay entry first, and the relay node then uses an optimised route to reach the exit. The entry-to-exit leg is still public internet, but the hop count is compressed and the most congested stretch of the default route is skipped.
- Best for: a fallback when a single direct route fluctuates
- Best for: mid-distance regions, everyday browsing and short videos
- Cost: mid-range, priced and performing between dedicated and direct
Direct route
The client handshakes directly with the exit node over the shortest path, relying entirely on how good the public international leg is at that moment. Peak hours can bring jitter; off-peak it often performs well, and this is the type with the widest country coverage.
- Best for: light browsing, research, latency-tolerant sites
- Best for: a quick look at pages and prices in a given region
- Cost: lowest, which is why direct routes are the most widely spread
| Route type | Path characteristics | Best for | Cost |
|---|---|---|---|
| Dedicated | Fixed end-to-end channel; the international leg avoids congested public exits | Live streams, meetings, long-lived sessions, large file transfers | Highest |
| Relay | Connect to a relay entry first, then an optimised route to the exit | Everyday video, web pages, short clips; fallback when direct routes fluctuate | Mid-range |
| Direct | The client handshakes directly with the exit node over the shortest path | Research, light browsing, checking regional pages | Lowest |
A single region usually has all three types. If one dedicated route performs poorly where you are, try another dedicated route in the same region first, then consider a relay; switching regions often fixes speed while creating a new region-detection problem.
Choosing a route by use case
The order you try routes in matters more than “which one is best”. Below are first choices and fallbacks for five use cases — when something goes wrong, work down the list instead of tapping at random. All routes use military-grade encryption; switching routes only changes the exit and the path, not your account or plan.
| Use case | First choice | Fallback | Notes |
|---|---|---|---|
| Everyday browsing | Direct | Relay | Pages, email, documents — short, retryable requests that tolerate latency |
| Video | Dedicated | Relay | 4K playback needs sustained bandwidth; first-frame load depends on path quality |
| AI Tools | Dedicated | Relay | Long-lived sessions; a mid-generation drop means starting over |
| Gaming | Dedicated | Direct | Jitter matters more than bandwidth; stay in the same region as the game server |
| Work | Dedicated | Relay | Meetings and collaboration tools are the most packet-loss sensitive |
Everyday browsing
Pages, email and documents are short, fragmented, retryable requests — a slightly slow moment barely affects the experience. Direct routes have the shortest path and are the default here; if a page stalls on one leg, a relay usually gets it through. There is no need to use a dedicated route for browsing — save those for cases that need stability.
Video
4K playback needs sustained bandwidth rather than an instantaneous peak, while first-frame load depends on path quality. The advantage of a dedicated route at peak hours shows up as no stalling and no bitrate drop; if the path from where you are to the dedicated entry is itself poor, a relay can be steadier. If playback keeps buffering, switch routes within the same country first, then consider another country.
AI Tools
AI tool requests are long-lived: one generation can run for tens of seconds to several minutes, and a mid-way disconnect means starting over. This is the least packet-loss-tolerant case, so dedicated routes come first; if conversations keep stalling mid-generation, a relay in the same region works better than a route in a more distant region.
Gaming
Gaming is about jitter, not bandwidth. A few tens of milliseconds of jitter is enough to change how controls feel, so dedicated routes come first, followed by direct routes in the same region as the game server. Cross-region gaming is hard to stabilise even with plenty of bandwidth — pick a route by where the server is, not by the region you use most.
Work
Meetings and collaboration tools are the most packet-loss sensitive: loss shows up directly as choppy audio or a frozen picture. Dedicated routes first, relays as fallback; if you are the only one dropping out of a meeting, switch routes first, then check your local network and router load.
Common route questions
These are the most common route questions; the answers cover routes and subscriptions only. Account, billing and client installation details live in the Help Centre and Guides.
How does the route count in the table relate to the 150+ routes?
The table lists representative routes for each region to show route types and coverage; it is not the full set. The 150+ routes on the page is the total number the service currently offers — the complete list expands by region inside the client, and switching routes also happens there.
Is a dedicated route always faster than a direct one?
Not necessarily. A dedicated route guarantees a stable path and low jitter; a direct route can perform just as well off-peak. The value of a dedicated route shows up at peak hours, over long cross-region distances and on long-lived connections; for looking things up during the day, direct is plenty.
Do I need to sign in again or re-import the subscription when switching routes?
No. Just select another route in the client — account status, remaining data and the plan period are unaffected. The subscription is imported once during setup; switching routes afterwards needs no repeat steps.
How many devices can use one route at the same time?
Unlimited. One subscription works on Windows, macOS, iOS, Android and Linux at the same time, and route selection is independent on each device — one does not override another.
The streaming column lists a platform — why do I still get a region error?
Platforms decide using account region, payment region and exit IP together; the route is only one part. Where the account itself is registered is often more decisive than the route — confirm the account and payment region first, then adjust routes. That is the more efficient order.
Routes first, plan second
Monthly subscriptions start at ¥9.9 and include 60GB, with data resetting each month on the activation date; unlimited devices, a 60-day money-back guarantee, and no email address needed to sign up. Payment supports Alipay / WeChat / USDT.