Sample routes by region
Each row lists four static facts only: country, city, route type and streaming support. The page shows no latency in milliseconds, no load percentage and no real-time bandwidth — the same route performs very differently across broadband providers and times of day, so a single instantaneous number doesn't help you choose. Pick the route type by use case first, then switch endpoints inside the client.
Asia-Pacific
Sample routes| Country / region | City | Route type | Streaming support |
|---|---|---|---|
| Japan | Tokyo | IEPL dedicated | Netflix / YouTube / Disney+ |
| Japan | Osaka | Relay | YouTube / Abema |
| South Korea | Seoul | IEPL dedicated | Netflix / YouTube |
| Singapore | Singapore | IEPL dedicated | Netflix / Disney+ / YouTube |
| Hong Kong | Hong Kong | Relay | Netflix / YouTube / HBO Max |
| Malaysia | Kuala Lumpur | Direct | YouTube |
| Thailand | Bangkok | Direct | YouTube / Netflix |
| India | Mumbai | Relay | YouTube |
| Vietnam | Ho Chi Minh City | Direct | YouTube |
North America
Sample routes| Country / region | City | Route type | Streaming support |
|---|---|---|---|
| United States | Los Angeles | IEPL dedicated | Netflix / Disney+ / HBO Max |
| United States | San Jose | Relay | Netflix / YouTube |
| United States | Seattle | Direct | YouTube |
| United States | New York | Relay | Netflix / HBO Max |
| Canada | Toronto | Relay | Netflix / YouTube |
| Canada | Vancouver | Direct | YouTube |
Europe
Sample routes| Country / region | City | Route type | Streaming support |
|---|---|---|---|
| United Kingdom | London | IEPL dedicated | BBC iPlayer / Netflix |
| Germany | Frankfurt | Relay | Netflix / YouTube |
| France | Paris | Relay | Netflix / Disney+ / YouTube |
| Netherlands | Amsterdam | Direct | YouTube |
| Switzerland | Zurich | Direct | YouTube |
| Sweden | Stockholm | Direct | Netflix |
| Spain | Madrid | Direct | YouTube |
| Italy | Milan | Direct | YouTube |
Rest of the world
Sample routes| Country / region | City | Route type | Streaming support |
|---|---|---|---|
| Australia | Sydney | Relay | Netflix / YouTube |
| New Zealand | Auckland | Direct | YouTube |
| United Arab Emirates | Dubai | Relay | YouTube |
| Brazil | São Paulo | Direct | YouTube |
| South Africa | Johannesburg | Direct | YouTube |
| Turkey | Istanbul | Direct | YouTube |
The table shows sample routes; the full list expands by region inside the client. Routes are adjusted as network conditions change, so whatever the client shows is what applies.
How route types work and what they cost
The three tiers differ in three things: whether the cross-border segment is exclusive, whether traffic passes through an intermediate hop, and the cost per unit of bandwidth. The same city may have both a dedicated and a relay endpoint — different labels, different experience and price, so check before you choose.
IEPL dedicated
Dedicated cross-border segment- How it works
- Traffic runs end to end over a fixed Ethernet leased line; the carrier provides a point-to-point channel for the cross-border segment, and the intermediate links aren't shared with other traffic.
- Best for
- Long video during the evening peak, cross-border video calls, large file transfers that need sustained upstream for hours, and workflows that can't tolerate a dropped connection.
- Cost difference
- The highest of the three: cost per unit of bandwidth is several times that of a standard relay, so dedicated endpoints are concentrated in major cities rather than every region.
Relay
Separate entry and exit- How it works
- You connect to the nearest entry node first, then the entry node forwards to the exit node over an optimised path. The cross-border segment follows a planned route instead of letting the local public internet connect straight to an overseas data centre.
- Best for
- Day-to-day browsing, streaming and AI tools — cases that need stability but not dedicated bandwidth. It's the compromise between extra hops and cost.
- Cost difference
- In the middle. The extra hop adds round-trip time, but you get less packet loss and steadier evening-peak performance, so value for money is usually the best of the three.
Direct
No intermediate hop- How it works
- The client connects straight to the exit node with no intermediate hop. Link quality depends on the public internet path from your local network to that data centre.
- Best for
- Nearby access, single-site lookups, and anything sensitive to round-trip latency but light on traffic; also a good backup endpoint alongside dedicated and relay routes.
- Cost difference
- The lowest of the three. The trade-off is an uncontrolled path: evening-peak variation is more noticeable than on dedicated or relay routes, so it isn't suited to long high-bitrate playback.
Route picks by use case
Choose by use case first, budget second. The five scenarios below are ordered by intensity of use, each with a preferred route type and the reason; you can switch at any time within one subscription, so there's no need to buy separately for different uses.
Everyday browsing and research
Preferred: relay / directWeb pages, email and documents are mostly short connections with small transfers, so sustained bandwidth matters little. A nearby relay node pulls the cross-border segment onto an optimised path; off-peak, a direct node is enough, and direct gives better value on a tight budget.
Long video and 4K playback
Preferred: IEPL dedicated4K playback needs a sustained high bitrate over a long period, and any mid-stream slowdown triggers buffering. A dedicated line's cross-border segment is exclusive, so it's less likely to be squeezed by other traffic at peak times. If you have several devices at home, put the TV or set-top box on the dedicated line and let the rest use relay.
AI tool conversations
Preferred: relay / dedicatedChat tools hold long-lived connections: requests are spaced out, but the session can't drop. A relay node's optimised routing reduces packet loss, and a dedicated line is steadier over long sessions. If answers cut off or hang, switch to another route in the same region first, then consider another region.
Gaming
Preferred: nearby direct / relayGames are most sensitive to round-trip latency and not very demanding on bandwidth. Pick the geographically closest endpoint, ideally in the same or an adjacent region; a cross-continent dedicated line is stable, but physical distance still adds latency, so it isn't the best main route for gaming.
Cross-border work
Preferred: IEPL dedicated + relay backupVideo calls, code repository sync and internal systems all need a connection that stays up. Use a dedicated line as the main route and keep a relay route in the same region as a backup in the client; switch manually if the main route misbehaves, rather than hunting for a route mid-meeting.
Coverage and getting started
The service covers 120+ countries / 150+ routes, and one subscription covers unlimited devices — phone, computer and tablet can be online at the same time. No email address is needed to register: a username and password are enough. After signing in, import the subscription in the client to see the full route list.
Monthly plans
- ¥9.9 / month60GB / month
- ¥18 / month250GB / month
- ¥28 / month500GB / month
Traffic resets each month on your activation date; when you upgrade mid-cycle, the price difference is prorated over the remaining days.
Data packs
- ¥158300GB
- ¥3581000GB
- ¥6583000GB
Use them until they run out — they never expire; ideal if your usage varies and you'd rather not renew monthly.
The client supports five platforms — Windows / macOS / iOS / Android / Linux — and you can get the client and your subscription right after signing in. Payment methods are Alipay / WeChat Pay / USDT. The first payment is covered by a 30-day money-back guarantee: just open a ticket, no reason required.
FAQ
Five common questions about the route list, the order to pick routes in, and billing.
Are the cities in the table all the nodes?
No. The table lists sample routes per region so you can compare route types and streaming support; the full list expands by region inside the client and covers 120+ countries / 150+ routes.
Why aren't latency figures shown?
Latency varies with your local broadband, the time of day and the destination site, so a fixed number on a page can't represent how it will perform on your network. A more practical approach: choose the route type by use case, then try endpoints in the same region inside the client.
Is an IEPL dedicated line always faster than relay?
Not necessarily. A dedicated line's advantage is an exclusive, stable cross-border segment, which shows most at peak times; if the destination is nearby, a relay or even a direct route has a shorter round trip. Choose by use case, not by the label alone.
How many devices can use one subscription at the same time?
Unlimited. One subscription works on Windows / macOS / iOS / Android / Linux at the same time, and each device picks its own route independently.
Do I need to buy a new plan if I move to another city?
No. Routes can be switched inside the client at any time, and your subscription and traffic don't change with region; monthly plan traffic resets each month on your activation date, and upgrading mid-cycle prorates the difference over the remaining days.