Server List · 120+ Countries / 220+ Routes

Server Locations & Route Selection Guide

The table below groups the main landing cities by region, along with line type and streaming support. IEPL dedicated lines run over a private cross-border channel, relay routes forward through a path-optimised entry point, and direct routes connect the client straight to the overseas landing node. The three types map to three different use cases, so check your purpose before you choose.

120+ Countries / 220+ Routes
Unlimited devices online at once
7-day no-questions-asked refund
No email address needed

Try for Free View Plans

Windows
macOS
Android
Linux

Singapore
Japan
Hong Kong
United States
Australia

Singapore · IEPL Dedicated Line Japan · Relay Hong Kong · IEPL Dedicated Line United States · IEPL Dedicated Line Australia · Relay Shadowsocks VLESS Hysteria2 Trojan Windows macOS Android Linux Singapore · IEPL Dedicated Line Japan · Relay Hong Kong · IEPL Dedicated Line United States · IEPL Dedicated Line Australia · Relay Shadowsocks VLESS Hysteria2 Trojan Windows macOS Android Linux

Server list grouped by region

Each row in the table is a landing city. "Line Type" tells you whether the route runs over a private cross-border channel, a path-optimised relay entry, or a direct client connection to the overseas landing node; the "Streaming" column notes how that city's node performs on common streaming platforms. The table lists the main landing points — the full route list is the live one inside your client subscription, and routes are added or removed as carrier links change.

Asia Pacific

Asia Pacific is the most heavily used group of routes for cross-border access: Singapore and Hong Kong run IEPL dedicated lines, so the cross-border leg never passes through public internet egress and sees less packet loss and jitter at peak hours; Japan, South Korea, Thailand and Malaysia are mostly relay routes, where the path from entry to landing is hand-picked, making them a good fit for everyday browsing and social media; Taipei, Ho Chi Minh City and Mumbai are direct routes with the shortest paths, suited to environments where the local network egress is already good. For streaming, prefer the four dedicated-line cities: Singapore, Tokyo, Hong Kong and Sydney.

Country / Region	City	Line Type	Streaming
Singapore	Singapore	IEPL Dedicated Line	Netflix / Disney+
Japan	Tokyo	IEPL Dedicated Line	Netflix / Disney+
Japan	Osaka	Relay	Netflix
Hong Kong	Hong Kong	IEPL Dedicated Line	Netflix / HBO
South Korea	Seoul	Relay	Netflix
Taiwan	Taipei	Direct	Netflix
Thailand	Bangkok	Relay	Netflix
Vietnam	Ho Chi Minh City	Direct	Netflix
Malaysia	Kuala Lumpur	Relay	Disney+
India	Mumbai	Direct	Netflix
Australia	Sydney	IEPL Dedicated Line	Netflix / Disney+
Australia	Melbourne	Relay	Netflix

North America

North American routes cover two kinds of needs. The first is streaming and AI tools, where services demand a stable egress IP and continuous links — Los Angeles and San Jose run IEPL dedicated lines, so long-lived connections are less likely to drop mid-session. The second is work and remote collaboration: Seattle, New York and Toronto are mostly relay routes, balancing coverage and cost. Of the two Canadian cities, Vancouver is a direct route, suited to scenarios that want a nearby landing point.

Country / Region	City	Line Type	Streaming
United States	Los Angeles	IEPL Dedicated Line	Netflix / HBO
United States	San Jose	IEPL Dedicated Line	Netflix / Disney+
United States	Seattle	Relay	Netflix
United States	New York	Relay	Netflix / HBO
Canada	Toronto	Relay	Netflix
Canada	Vancouver	Direct	Netflix

Europe

European routes centre on two dedicated-line cities, London and Frankfurt, covering the common access needs of the UK, Germany, France and the Netherlands; Paris and Amsterdam are relay routes, good for European services, academic databases and regional streaming; Istanbul is a direct route that fills in coverage toward south-eastern Europe. Round trips to Europe are long, so when choosing a route, look at link stability rather than comparing distance alone.

Country / Region	City	Line Type	Streaming
United Kingdom	London	IEPL Dedicated Line	Netflix / Disney+
Germany	Frankfurt	IEPL Dedicated Line	Netflix
France	Paris	Relay	Netflix / Disney+
Netherlands	Amsterdam	Relay	Netflix
Turkey	Istanbul	Direct	Netflix

Other regions

Landing cities in the Middle East, South America and emerging Southeast Asian markets mainly serve regional needs: Dubai covers business and cloud service access in the Gulf, São Paulo covers landings toward South America, and Jakarta fills in the Southeast Asian archipelago. These three run mostly as relay and direct routes and suit users with a clear regional requirement; if you don't need a specific region, there's no reason to pick them deliberately.

Country / Region	City	Line Type	Streaming
United Arab Emirates	Dubai	Relay	Netflix
Brazil	São Paulo	Direct	Netflix
Indonesia	Jakarta	Relay	Netflix

About the route list: The table above shows the main landing cities in each region; for the complete list, go by what's inside your client subscription. Routes are added and removed as carrier links change, and the list in your subscription updates automatically — no repurchase and no manual config edits. If you want to pick a route by purpose, head to the line type explanations and route tips below.

The three line types explained

The line type decides how your data travels from your device to the overseas landing node. Once you understand the difference between the three, you can explain why the same device feels completely different on a different route.

IEPL dedicated line

IEPL is a carrier-grade international Ethernet private line. The cross-border leg uses a dedicated point-to-point channel and never passes through public internet egress. From the entry point onward, traffic travels on a private link with guaranteed bandwidth, so the cross-border leg is largely insulated from public network congestion.

How it worksYour client connects to a dedicated-line entry point, and from there to the overseas landing node the carrier provides a private channel with fixed bandwidth, so the cross-border leg never competes with public traffic for egress.
Best for4K streaming at peak hours, long-lived connections and streaming output for AI tools, and packet-loss-sensitive work such as video calls and remote desktop.
CostHighest cost per unit of bandwidth, so these lines are deployed only in the busiest cities with the strictest stability requirements — fewer of them than the other two types.

Relay routes

Relay routes land first at a nearby entry point, which then forwards traffic to the overseas node over a hand-picked path. The cross-border leg still runs over the public internet, but the route from entry to landing has been tested and screened to avoid detours and heavily congested paths.

How it worksYour client connects to a nearby relay entry, which forwards traffic to the overseas landing node along a pre-tested path — saving you the trouble of testing routes yourself.
Best forEveryday browsing, social media and research, and for anyone who wants wider regional coverage without paying dedicated-line prices on every route.
CostBandwidth cost sits between dedicated lines and direct routes; this is the main way mid-popularity cities are covered, and the count is in the middle.

Direct routes

Direct routes connect your client straight to the overseas landing node with no relay entry in between, giving the shortest path and the fewest hops. When your local network egress is good, direct is often the least fuss.

How it worksThe client connects directly to the landing node with no extra forwarding step; the path is simply the shortest route from your local network to the landing city.
Best forNetworks with a solid local egress, quick lookups, and file downloads or background tasks where latency isn't critical.
CostLowest cost and the largest number of nodes — the bulk of the 120+ country coverage, and usually the easiest type for a new user to connect to on the first try.

How to decide which type to use: Start with how much stability the task needs, then how latency-sensitive it is. Tasks that need stability and long sessions should go to dedicated lines first; tasks that just need broad coverage and easy switching can use relay or direct. All three types are included in the same subscription — no separate purchase — and switching is just picking a different line in the client.

Route tips by use case

The best route for the same account depends on what you're doing. Below are route orders for five common use cases — start with the first and work down if it doesn't perform well.

Everyday browsing and research

First choice: nearest relay · Alternative: direct

Web pages, docs and social media come in short sessions with scattered requests — not latency-sensitive, but coverage-sensitive. Pick the relay route closest to you geographically, and switch to a direct route when you need a specific country for a while. This kind of use burns little data, so the 60GB monthly plan is usually enough.

Streaming video

First choice: IEPL dedicated line (Singapore / Tokyo / Hong Kong / Sydney)

Streaming needs steady throughput; any mid-playback jitter drops the picture quality or triggers a re-buffer, and dedicated lines show their biggest advantage at peak hours. Pick the region by the library you want, then choose a dedicated-line city within it; cities marked in the Streaming column tend to be more reliable for the matching platforms. For 4K, leave yourself enough data — the 250GB or 500GB monthly plan is more comfortable.

AI tools

First choice: IEPL dedicated line (United States / Japan / Singapore)

AI tools use long-lived connections with streaming output, so link continuity matters more than raw speed — a dropped stream cuts the answer off. Keep one dedicated line for the long term and avoid switching egress regions often; a consistent history on the same egress IP is friendlier to account stability. For tool-by-tool availability, see the AI Tools guide.

AI Tools guide

Online gaming

First choice: nearest IEPL dedicated line (Hong Kong / Tokyo / Singapore)

Games are the most sensitive to latency and packet loss and the least demanding on bandwidth. Pick a dedicated-line city that's physically close and stick with it — don't switch routes over a brief latency spike, since switching means a fresh handshake and hurts the experience more. If the game itself isn't region-sensitive, the nearest dedicated-line city is usually the steadiest choice.

Remote work and video meetings

First choice: a dedicated line in the same region as your company or team

Meetings and remote desktop are two-way real-time traffic, so stability matters more than top speed. Keep one dedicated line in your team's region for the long term and leave the client running; simultaneous connections are unlimited, so desktop, phone and tablet can all be online without swapping accounts. Data resets monthly on your activation date, and if you upgrade mid-cycle the price difference is prorated over the remaining days.

Coverage at a glance

The 120+ country coverage is made up of 220+ routes. Listed below are the higher-traffic regions covered in the table above; for anything else, search by region or city name in the route list inside your client subscription.

The line type explanations and route tips describe how to use the service, not a promise; real-world results depend on your local network, your carrier's egress quality and where the target service is hosted. Every plan includes all routes — no separate add-on for a specific region.

Route and plan FAQ

How should I read the Line Type labels in the table?

"IEPL Dedicated Line" means the cross-border leg runs on a private channel — the most stable option, good for streaming, AI tools and remote work. "Relay" means traffic is forwarded through a nearby entry along an optimised path — broad coverage and good value, good for everyday browsing. "Direct" means the client connects straight to the overseas landing node — the shortest path, good when your local egress is solid. All three types are in the same subscription, and switching costs nothing extra.

What's the main difference between IEPL dedicated lines, relay and direct?

The difference is how data travels from your device to the overseas landing node. Dedicated lines use a private channel from the carrier and never compete with public traffic for egress — at the highest cost per unit of bandwidth, which is why they only cover key cities. Relay routes land at a nearby entry first and forward along a hand-picked path; the cross-border leg is still public internet, but you skip the trial-and-error. Direct routes add no middle step, have the fewest hops and the largest number of nodes. The full breakdown of how each type works and what it costs is in the line type section above.

What does the Streaming column mean?

It shows how well that city's node works with the matching streaming platforms, to help you decide which region to pick. Platform regions and risk controls change over time, so actual availability is what you see when you use it; if a platform isn't working on a given day, switching to another route in the same region usually fixes it.

How many devices can use one subscription at the same time?

Unlimited simultaneous connections. Windows, macOS, iOS, Android and Linux can all sign in with the same account, and desktop, phone and tablet can be online at once at no extra cost. Data is counted against your plan total; monthly plan data resets each month on your activation date, and upgrading mid-cycle prorates the price difference over the remaining days.

How much do the plans cost, and can I get a refund if it's not right?

Monthly plans: ¥9.9/month with 60GB, ¥18/month with 250GB, ¥28/month with 500GB. Data packs: ¥158 for 300GB, ¥358 for 1000GB, ¥658 for 3000GB — use them until they run out, they never expire. Alipay, WeChat Pay and USDT are all accepted. Refunds within 7 days of purchase, no questions asked; see the refund policy page for how to request and how it's processed.

Do I need an email address to sign up?

No email address needed — just a username and password. Once you're set up, pick a plan in the dashboard and get your subscription. Your subscription link is an account credential, so don't share it publicly; if it leaks, you can reset it in the dashboard.