Route workspace · five-platform clients
One route workspace holds 120+ countries / 180+ routes: choose a route, connect and check your data in one place, with quantum encryption and unlimited simultaneous devices.
Routes are grouped by region and labelled with access type and streaming support, so you pick by type first and region second instead of reconnecting to test.
| Country/Region | City | Route type | Streaming |
|---|---|---|---|
| Japan | Tokyo | IEPL dedicated line | Supported |
| Singapore | Singapore | Relay | Supported |
| United States | Los Angeles | Direct | Supported |
| Hong Kong SAR | Hong Kong | IEPL dedicated line | Supported |
| Germany | Frankfurt | Relay | Supported |
IEPL dedicated lines run on a private path, so latency and jitter stay more predictable — a good fit for video calls, remote desktop and sessions that need to stay connected for hours. Relay routes hand traffic to the nearest entry node first and then forward it to the target region, which usually holds up better than direct routes during evening peak hours. Direct routes skip the relay entirely for the shortest path, and suit regions whose connections are already solid.
You do not have to commit to one route. You can switch at any time in the client; the current connection drops briefly during the switch, and your subscription and remaining plan data stay exactly as they were once you reconnect. If a route degrades at certain hours, moving to another route in the same region usually works better than reconnecting over and over.
The Streaming column shows how well a route handles the major local platforms. For 4K playback, prefer routes marked dedicated or relay, and keep the node region aligned with the platform's own region. The nodes page lists every route by region, so you can check it against the services you actually use before choosing.
The six items cover stability, encryption, device count, AI tools, streaming and refunds. Select an entry on the left to read the details; they follow the order you would actually use them in.
Current route, route type, remaining plan data and payment method all sit in the left column; the three pills on the right map to connection, subscription and data-pack status, readable at a glance.
Windows, macOS, iOS, Android and Linux each have a client, and the same subscription works on all five; simultaneous devices are unlimited, so phones and computers can stay connected together.
Stuttering at peak hours usually comes from congestion at the exit, not from a lack of local bandwidth. Routes are grouped by region and access type, with dedicated and relay routes carrying most of the traffic, and you can switch routes directly in the client instead of waiting for automatic failover. For video, video calls or large file transfers, prefer routes marked as dedicated; if a route gets jittery late in the evening, another route in the same region usually restores things and shortens the interruption. The route list labels each type, so you can judge what a route is good for before you connect. 20:00 to 24:00 is the heaviest window, and performance there says more about route quality than daytime peaks do.
Traffic between the client and the nodes is transferred with quantum encryption, and sign-in credentials and subscription details travel over the same encrypted channel — no extra toggle in settings. Encryption happens inside the client; the node side only forwards traffic and does not inspect it. The service keeps only the minimum account information needed to activate a plan, meter data usage and handle tickets: no browsing content is logged, and access records are not used for anything else. Sign-up needs only a username and password, with no email address required, so account data stays minimal. After switching devices, signing in again restores the same configuration with the same encryption.
Simultaneous devices are unlimited: one account can run on Windows, macOS, iOS, Android and Linux at the same time. The computers, phones and tablets at home do not have to sign each other out, and the laptop you take on a trip connects straight away. Each device keeps its own route preference, so switching routes on one device does not disturb connections on the others. Subscription and data are counted per account, not per device, so adding devices costs nothing extra and never forces a plan upgrade. If a device will sit idle for a long stretch, just disconnect it in the client — no extra steps in the dashboard.
Tools like ChatGPT, Claude and Gemini ask different things of a network in the browser and through the API: the browser side suffers from dropped streams, the API side from timeouts. The route list marks nodes suited to long-lived connections; when calling an API, set the timeout higher than the default and keep the same exit route where possible to cut down on retries caused by a changing exit. For concurrent requests, first confirm the client will not drop existing connections when you switch routes. A more detailed selection and self-check list is in how to choose AI API acceleration.
Netflix, Disney+, YouTube and HBO carry different catalogues per region, and whether a title plays depends on where your exit lands. The route table notes each route's streaming support; for 4K, prefer dedicated or relay routes and match the node region to the platform's region. Before you hit play, check whether the client is in global mode or per-app proxy — running a browser extension and the desktop client at the same time often creates two exits and the picture quality drops instead of improving. If a page opens but keeps buffering, another route in the same region works better than refreshing. More on regions and picture quality is on the streaming access page.
7-day refund, no questions asked: open a ticket in the user dashboard with your order number — no reason needed. Refunds go back through the original payment channel, and how long it takes depends on that channel. The rule covers both monthly plans and data packs; check that the order is still inside the 7-day window before you apply. Payment runs through Alipay, WeChat Pay or USDT, and orders and refund records stay in the dashboard for line-by-line checking. If you only want a different tier, a mid-term upgrade charges the prorated difference for the remaining days, which is usually less hassle than refunding and buying again.
Route coverage is something you can verify: 120+ countries and 180+ routes, labelled by region and access type rather than summed up in a single number. The nodes page lists each route's type and streaming support, so you can tell before ordering whether it covers where you need to go.
Pricing and rules are stated up front: three monthly tiers, data packs that last until used up and never expire, and a 7-day refund; payment via Alipay, WeChat Pay and USDT, and sign-up needs only a username and password — no email address.
Support runs through tickets in the user dashboard, with orders, subscriptions and refunds in the same place — no separate support mailbox to hunt for. If something goes wrong, work through the troubleshooting guide by symptom first, establish whether it is a local setting or a route problem, and then decide whether to open a ticket.
Clients and subscriptions are both obtained in the user dashboard: sign up, choose a plan and sign in, then download the client for your platform and import the subscription. Installer links are not published on this page.
After installing on Windows or macOS you need to grant network permission: the system shows a single confirmation dialog, and only after you allow it can the client take over traffic. If you declined once, that is fine — re-enable it under Network or Privacy in system settings.
On iOS, install from the App Store; on Android and Linux, download the matching build following the instructions in the user dashboard. After importing the subscription, connect once and confirm the client shows Connected, then open a browser and load an international site to verify — that way a local DNS problem is not mistaken for a route problem.
One account can sign in on several devices without them affecting each other, and you do not need to sign out of the old device first. The subscription URL is only provided inside the user dashboard; please do not forward it, because a link shared with many people will affect your own connection quality.
Monthly plans come in three data tiers, and data resets every month on your activation date; data packs last until used up and never expire. A mid-term upgrade charges the prorated difference for the remaining days, with no new order needed.
¥9.9/mo
60GB · data resets monthly on your activation date
¥18/mo
250GB · data resets monthly on your activation date
¥28/mo
500GB · data resets monthly on your activation date
If your monthly data runs short, you can buy a data pack on its own: ¥158/300GB, ¥358/1000GB, ¥658/3000GB. Packs do not reset monthly and last until used up, which suits short bursts of heavy use or a standby reserve.
For browsing, email and the occasional video, the 60GB tier is usually enough; an hour or two of HD video a day plus regular AI tools sit more comfortably in the 250GB tier; with several devices online at home, frequent 4K playback or API requests, the 500GB tier cuts down on mid-month top-ups.
Data resets every month on your activation date rather than on the calendar month, so starting mid-month or at month end costs you nothing. To upgrade mid-term, the difference is prorated over the remaining days, no new order is needed, and data already used is not reset.
If you are unsure, start on a lower tier and upgrade or add a data pack when you need to; packs last until used up and never expire, so buying early wastes nothing and works well for short bursts or as a reserve.
How to choose a route, how to verify a connection once it is up, whether a long-term subscription pays off — all of it lives in the blog, one question per post with steps you can actually follow.
Connecting is not the same as getting through: three steps — exit IP, DNS lookup and a per-app test — confirm whether traffic really takes the international route, plus the usual cases of false connectivity.
Read the full articleFrom downloading the client and granting system network permissions to importing the subscription, verifying connectivity and handling permission dialogs — one complete macOS setup, step by step.
Read the full articleA working browser session does not mean the API will run: what to watch for in fixed exits, concurrent connections and timeout settings, with a selection and self-check list for developers.
Read the full article