Route overview
Route overview by region
The table below groups routes into four regions — Asia Pacific, North America, Europe and Other — and lists some of the cities with their route types. The “Streaming support” column shows how each route performs on common streaming sites: routes marked “Supported” trigger fewer checks during everyday playback and seeking, while routes marked “Partial” work but may need a retry on another route.
| Country / region | City | Route type | Streaming support |
|---|---|---|---|
| Asia Pacific | |||
| Japan | Tokyo | IEPL dedicated line | Supported |
| Japan | Osaka | Relay | Supported |
| Singapore | Singapore | IEPL dedicated line | Supported |
| Hong Kong | Hong Kong | IEPL dedicated line | Supported |
| South Korea | Seoul | Relay | Supported |
| Malaysia | Kuala Lumpur | Relay | Partial |
| Thailand | Bangkok | Relay | Partial |
| Vietnam | Ho Chi Minh City | Relay | Partial |
| Australia | Sydney | Direct | Supported |
| Australia | Melbourne | Direct | Partial |
| India | Mumbai | Direct | Partial |
| Philippines | Manila | Direct | Partial |
| North America | |||
| United States | Los Angeles | IEPL dedicated line | Supported |
| United States | San Jose | Relay | Supported |
| United States | Seattle | Direct | Supported |
| United States | New York | Relay | Supported |
| United States | Dallas | Direct | Partial |
| Canada | Toronto | Relay | Supported |
| Canada | Vancouver | Direct | Partial |
| Mexico | Mexico City | Direct | Partial |
| Europe | |||
| United Kingdom | London | IEPL dedicated line | Supported |
| Germany | Frankfurt | Relay | Supported |
| Netherlands | Amsterdam | Relay | Supported |
| France | Paris | Direct | Partial |
| Switzerland | Zurich | IEPL dedicated line | Supported |
| Sweden | Stockholm | Direct | Partial |
| Spain | Madrid | Direct | Partial |
| Poland | Warsaw | Direct | Partial |
| Other regions | |||
| United Arab Emirates | Dubai | Relay | Partial |
| Turkey | Istanbul | Direct | Partial |
| Israel | Tel Aviv | Direct | Partial |
| Brazil | São Paulo | Direct | Partial |
| Argentina | Buenos Aires | Direct | Partial |
| South Africa | Johannesburg | Direct | Partial |
The table above is a sample of routes, not the full list. Coverage currently stands at 110+ countries / 160+ routes; the complete list opens by region in the route list after signing in and inside the client.
Route type
Three route types: IEPL dedicated lines, relay and direct
Route type describes how data travels from the entry point to the exit. Two routes in the same country can behave very differently at peak hours depending on whether they use a dedicated line, a relay or a direct connection. All three types are included in the subscription and shown grouped by region and type; select one to switch, with no configuration changes.
01
IEPL dedicated line
International Ethernet Private Line: an isolated channel between the two ends that does not share capacity with ordinary public internet traffic. The cross-border leg avoids the congestion points of the public path, so jitter at peak hours is lower and long-lived connections are less likely to drop.
- 4K streaming and seeking at peak hours
- Video calls, remote desktop and other long-lived connections
- Real-time work that is sensitive to packet loss
Cost tierHigh
02
Relay
Traffic first lands on a nearby relay node, which then connects through to the target region. The cross-border leg follows an optimised path and the last leg returns to the public internet. Cost and stability sit between dedicated lines and direct routes, which makes it the default choice for most use cases.
- Everyday browsing and research
- AI Tools and web apps
- Streaming and most office work
Cost tierMedium
03
Direct
The client connects straight to the destination data centre with no extra hop in between. The path is the shortest and the cost the lowest, but the cross-border leg depends entirely on the public internet at that moment, so peak-hour variation is more noticeable than on a dedicated line.
- Reaching smaller regions and single sites
- Quick lookups and file downloads
- Cost-sensitive use where stability matters less
Cost tierLow
The cost difference comes from how bandwidth is purchased. Dedicated lines are bought as fixed, exclusive capacity, so the unit price is highest. On relays, the cross-border leg is scheduled by the provider and shared across users on the same optimised path, so the price sits in the middle. Direct routes use no intermediate segment, so they cost the least. What separates the three is not whether they connect, but how steady they stay once connected.
The three types are not substitutes for one another either. A single region often offers both dedicated and relay routes: dedicated lines hold up better at peak hours, while relays are close behind during the day. For everyday use, start with a relay and switch to the dedicated line in the same region if you hit buffering, dropped streams or a call that cuts out. Conversely, if you only connect late at night, there is no need to hold a dedicated line.
When a region offers both dedicated and relay routes, you do not have to start with the dedicated one. Run the relay for a full day and watch for buffering at peak hours; switching only when it appears costs less than holding a dedicated line the whole time.
Choosing a route
Choosing a route: match the route type to your use case
Picking a route takes three steps: identify the region the target service sits in, choose a route type for the use case, then fine-tune by time of day. The region decides the exit point and has no substitute; the use case decides the type; the time of day decides whether you need a steadier route at peak hours.
-
Everyday browsing and search
Mostly pages and images: small requests, short connections, so a relay path is enough. It is steadier than direct at peak hours and does not take up dedicated capacity.
-
4K streaming
High-bitrate playback is sensitive to jitter: once the buffer empties, the spinner appears. The cross-border leg of a dedicated line is steadier, so start-up and seeking involve less waiting.
-
AI Tools
Streaming output depends on a long-lived connection, and a dropped stream cuts the answer off mid-sentence. These cases call for stability first, not peak bandwidth.
-
Online gaming
Games care about round-trip latency and packet loss, not download speed. Start with the nearest Asia Pacific node, then check whether that node uses a dedicated line; the specific server region still has to match where the game's servers are.
-
Remote work and meetings
A meeting can run for over an hour, and a dropped connection means rejoining. For these cases, stay on one dedicated line rather than switching often.
-
Research on smaller regions
For a single site, direct is the cheapest option and there is no need to tie up a dedicated line for a one-off task; if pages keep failing to load, move to a relay in the same region.
Looking at all six scenarios together, the order of judgement is really just one line: lock the region first, then pick the type within it. Choose the wrong region and no route type will help; once the region is right, the difference between types shows up at peak hours and on long connections.
Time of day is the last variable. Congestion on cross-border links follows a clear daily pattern, with public exit capacity under the most pressure from evening into late night, when direct routes and some relays are more likely to buffer. If your usage is concentrated in the evening, set a dedicated line as the default rather than switching each time a problem appears.
Regional groups
Regional groups: Asia Pacific, North America, Europe and other
Routes within the same region are closer in round-trip latency and availability; across regions, geographic distance and route type compound. Below is what each of the four regions suits, and what to watch for when choosing a route inside it.
Asia Pacific
Japan, Singapore, Hong Kong and South Korea are the closest exit points from mainland China, usually with the lowest round-trip latency. For Asia Pacific streaming, Asia Pacific game servers and services aimed at Asia, pick from this group first. Asia Pacific also has the highest density of dedicated lines, so stability at peak hours is best here.
North America
On the US west coast, Los Angeles, San Jose and Seattle are closer to Asia and are the usual entry points for US services and AI tools; New York suits sites aimed at the US east coast. Routes in Canada and Mexico cover the rest of North America and suit cases with a clear regional requirement.
Europe
London, Frankfurt, Amsterdam and Zurich are the main European exit points, suited to European sites and European streaming. The path from Asia is longer, so prefer a dedicated line or relay; direct routes vary more at peak hours and suit cost-sensitive use spread across the day.
Other regions
Routes in the Middle East, South America, Africa and West Asia are mainly direct and relay, for cases with a clear regional need such as reaching local sites or local services. These regions have fewer routes than Asia Pacific and North America, so prioritise whether a connection is stable before considering speed.
Getting your routes
How to view the full route list
The table shows only some cities; the full route list is available in the client after signing in. There are five steps, and each one is covered in more detail in the guides.
- Create an account: no email address required — a username and password are enough.
- Choose a plan: monthly plans are ¥9.9/month for 60GB, ¥18/month for 250GB and ¥28/month for 500GB. Data resets each month on the activation date, and mid-cycle upgrades are prorated against the remaining days. Alternatively, pick a data pack: ¥158 for 300GB, ¥358 for 1000GB or ¥658 for 3000GB — use it up at your own pace, it never expires.
- Get the client: after signing in, download it for your platform from the download page — Windows / macOS / iOS / Android / Linux are supported.
- Import the subscription: once imported in the client, routes are grouped by region and type; select one to switch, with no configuration changes.
- Check the connection: open the target site or app and confirm the exit region is correct; for streaming, play a segment and then seek to confirm it holds up.
There is no limit on simultaneous devices: mobile, desktop and tablet can sign in to the same account at once and share the same data allowance. Payment options are Alipay / WeChat / USDT. If you are not sure which route to start with, begin with a relay and switch to a dedicated line as needed; for more detailed client instructions, see the guides.
FAQ
Common questions about routes and picking one
Why does the table list only some cities?
The table is a sample, meant to compare route types across regions; the full list opens by region in the route list after signing in and inside the client. Coverage currently stands at 110+ countries / 160+ routes, and a single region usually offers both dedicated and relay routes.
What is the difference between an IEPL dedicated line and a relay?
The cross-border leg of a dedicated line runs on an isolated channel and does not share capacity with public traffic, so jitter at peak hours is lower. A relay first lands on a nearby node and then hands off to the target region, with cost and stability between dedicated lines and direct routes. Both are included in the subscription, and switching between them takes no extra steps.
How many devices can use one subscription at the same time?
There is no limit on simultaneous devices. Mobile, desktop and tablet can sign in to the same account at once and share the same data allowance.
A route suddenly slowed down — what should I check first?
First switch to another route in the same region inside the client, then check whether your local network is healthy. When the cross-border leg is congested at peak hours, a dedicated line is usually steadier than a direct route; if every route in the same region is affected, open a ticket in the user panel.
How do I get the full route list after subscribing?
Sign in to the user panel, download the client for your platform from the download page and import the subscription to see the full route list. Windows / macOS / iOS / Android / Linux are supported; the exact import and switching steps are in the guides.
How does the refund work?
A 14-day no-questions-asked refund is available; the refund window and how to request one follow the terms of service.
More setup detail is in the guides, pricing and refunds in plans and pricing; for route pairings with streaming and AI tools, see Streaming and AI acceleration.