Route List

Server Locations and Global Routes

Coverage currently stands at 120+ countries and 190+ routes, maintained in groups for Asia-Pacific, North America, Europe and other regions. The table below lists representative cities and route types for each region; a single city may have several different routes, and the list in the client shows them separately by type. The table holds static facts only and does not display latency or load figures.

Start Free View Plans

Route Overview: grouped by region

A single city can have several routes at once. The Route Type column shows the most commonly used option for that city; once you sign in, the client lists every route for that city separately, and you can filter by region or by type.

Asia-Pacific

11 representative routes · Common exits toward mainland China and East Asia
Country/RegionCityRoute TypeStreaming Support
Singapore SingaporeIEPL dedicated line NetflixDisney+AI Tools
Hong Kong SAR Hong KongIEPL dedicated line NetflixYouTube 4KAI Tools
Japan TokyoRelay NetflixAnime platformsAI Tools
Japan OsakaDirect YouTube 4K
South Korea SeoulRelay StreamingGaming
Taiwan TaipeiRelay Netflix
Malaysia Kuala LumpurDirect —
Thailand BangkokDirect —
Vietnam Ho Chi Minh CityDirect —
Philippines ManilaDirect —
Australia SydneyRelay Streaming

North America

6 representative routes · Main exits for AI tools and US streaming
Country/RegionCityRoute TypeStreaming Support
United States Los AngelesIEPL dedicated line ChatGPTClaudeNetflix
United States San JoseDirect AI ToolsGemini
United States SeattleRelay —
United States DallasRelay —
Canada TorontoRelay Streaming
Canada VancouverDirect —

Europe

10 representative routes · Relay hubs and dedicated line exits toward Europe
Country/RegionCityRoute TypeStreaming Support
Germany FrankfurtIEPL dedicated line AI ToolsNetflix
United Kingdom LondonIEPL dedicated line BBC iPlayerNetflix
Netherlands AmsterdamRelay Streaming
France ParisRelay Netflix
Belgium BrusselsDirect —
Spain MadridDirect —
Switzerland ZurichDirect —
Sweden StockholmDirect —
Poland WarsawDirect —
Turkey IstanbulDirect —

Other Regions

6 representative routes · Additional exits toward the Middle East, Africa and South America
Country/RegionCityRoute TypeStreaming Support
Israel Tel AvivRelay —
Egypt CairoDirect —
Tunisia TunisDirect —
Argentina Buenos AiresDirect —
Chile SantiagoDirect —
Colombia BogotáDirect —

The table above shows representative routes for each region, covering 120+ countries and 190+ routes in total; different routes in the same city are listed separately in the client. A dash (—) means the route has no specific streaming support listed, not that the site in question is unreachable. The table does not include latency, load or bandwidth figures — that data changes with time and your local network, and is only shown by the client while connected.

The route list changes as data centers are adjusted. If a city is temporarily missing from the client, the route is usually under maintenance; switch to another city in the same region in the meantime — the remaining data on your plan is unaffected.

Route Types explained: IEPL dedicated line / Relay / Direct

The route type decides which path your data takes from your location to the exit data center. The three types are not substitutes for one another but a combination covering different distances and stability needs: work out when you connect and in which direction, and choosing a route stops being guesswork.

IEPL dedicated line

Highest cost

How it worksTraffic runs from the local entry point to the exit data center over a carrier dedicated line, avoiding congested public internet backbone segments; the path is fixed and bandwidth is not shared with other users.

Best forLong, stable work sessions, AI tool conversations, cross-border video meetings, and anything that has to stay usable during evening peak hours.

CostDedicated line capacity is billed by bandwidth, making this the most expensive of the three types, so it is only deployed between popular cities and international exits — the smallest set of routes.

NoteA dedicated line does not reroute mid-path; if the link fails, traffic moves to a backup dedicated line, so connection quality fluctuates less than on public routes.

Relay Routes

Moderate cost

How it worksYou connect first to the nearest relay entry data center, which forwards traffic to the target exit; the relay leg runs over optimized internal links, and only the final hop touches the public internet.

Best forRegions far from the exit, such as connecting from Asia to Europe or South America; suitable for streaming and everyday browsing, and the widest-reaching type.

CostPriced between dedicated line and direct, with entry and exit capacity that scales separately, so relay routes are the most numerous; new cities usually launch as relay first.

NoteWith one extra hop, it can add a few milliseconds in the worst case, which usually buys fewer cross-border detours.

Direct Routes

Lowest cost

How it worksThe client connects straight to the exit data center in the target region with no extra relay node in between — the shortest path.

Best forCases where the target region is close to you, or where the exit location matters — for example, when the exit IP needs to be in the same country as the site you are visiting.

CostThe cheapest of the three and the widest city coverage, well suited as a backup alongside your main route.

NoteDirect quality depends on the public internet path from your network to the exit data center and may fluctuate at peak hours, so keep a relay or dedicated line ready as well.

Choosing a Route: pick by use case

One account covers unlimited devices, with five online at the same time, and each device can pick its own route. Below are pairing ideas by use case: choose the route type by what you are doing, then the city by direction.

Everyday browsing and search

Nearest directBackup: relay

Browsing and research are not latency-sensitive, but they do care about a stable connection. Start with a direct route in the geographically closest city — users in eastern or southern China, for example, pick Hong Kong, Japan or Singapore; if peak-hour fluctuations appear, switch to a relay route in the same region. Everyday use does not need to occupy dedicated line capacity.

Streaming and 4K video

Hong Kong / Japan / SingaporeIEPL dedicated line or relay

4K playback needs sustained, steady bandwidth and suffers most when jitter forces a re-buffer. For Hong Kong, Japan and Southeast Asia catalogs, prefer the IEPL dedicated lines in Hong Kong, Japan and Singapore; for US catalogs, take the Los Angeles dedicated line or the Seattle and Dallas relays. Connect the route before opening the player so you never switch exits mid-stream.

AI tools and long sessions

United States / JapanIEPL dedicated line

AI tools demand two things from a network: a consistent exit region over time, and long connections that do not drop. If a streaming response disconnects, the whole conversation has to start over. Keep one US or Japan dedicated line as your fixed route and avoid switching cities mid-conversation; the same applies to API calls — pin the exit.

Gaming and real-time matches

Nearest + directIEPL dedicated line

Games are the most latency-sensitive, so pick by physical distance first: stay in the same city or region rather than crossing continents. For Asian servers, prefer Hong Kong, Tokyo and Seoul; for European servers, Frankfurt and London. Test the connection once before you enter a match and start only when it is steady — switching routes mid-game drops you.

Work and remote meetings

IEPL dedicated lineKeep a backup ready

Remote meetings, repository syncs and file uploads are the most packet-loss-sensitive, so use an IEPL dedicated line and pin the exit. At the same time, save a relay route in the same region as a backup in the client, so you can switch the moment the main route goes into maintenance without hunting for a city again.

Coverage and Regional Distribution

Routes cover 120+ countries and 190+ routes, concentrated in three directions — Asia-Pacific, North America and Europe — with additional exits in the Middle East, Africa and South America. One account covers unlimited devices, with five online at the same time, and each device can connect to a route in a different region.

Asia-Pacific: Singapore · Hong Kong · Tokyo · Osaka · Seoul · Taipei · Sydney North America: Los Angeles · San Jose · Seattle · Dallas · Toronto · Vancouver Europe: Frankfurt · London · Amsterdam · Paris · Zurich · Stockholm Other: Tel Aviv · Cairo · Buenos Aires · Santiago · Bogotá

The cities above are representative for each direction; the full list is the one shown in the client. Signing up needs only a username and password — no email address; payment is available via Alipay, WeChat Pay and USDT; every plan includes a 14-day money-back guarantee.

FAQ

Common questions about the route list, route types and choosing a route. For more, browse the Help Center by category.

Are all the cities in the table guaranteed to be in the client?

The table lists representative routes for each region; the client shows every route currently available, grouped by region and route type. A few cities are temporarily removed from the list while their data center is under maintenance and return once it is done — the remaining data on your plan is unaffected.

Why does the route list not show latency and bandwidth figures?

Latency and bandwidth change with your local network, carrier routing and time of day, so hard-coding them on a page would often not match what you actually get. The page keeps only the facts that do not change: country, city, route type and streaming support; live figures are shown by the client while connected.

Should I choose an IEPL dedicated line or a relay route?

Two things decide it: how long the connection lasts and whether it crosses continents. Long online work and AI tool sessions favor a dedicated line; for cross-continent access or less common cities, relay routes take fewer detours and come in greater numbers. Save both and switch by scenario.

Can one account connect to routes in different regions at the same time?

Yes. One account covers unlimited devices, with five online at the same time — Windows, macOS, iOS, Android and Linux each connect to their own route without affecting the others, which suits setups like one machine streaming US catalogs while another connects to Japan for work.

Do monthly subscriptions and data packs both get access to all routes?

Yes, both. Monthly plans: ¥9.9/month with 60GB, ¥18/month with 250GB and ¥28/month with 500GB, reset each month on your activation date; data packs: ¥158/300GB, ¥358/1000GB and ¥658/3000GB, valid until used up with no expiry. There is no difference in route access between the two.

Are new routes added, and how often is the list updated?

Yes. New cities usually launch as relay routes first, and once they have run steadily for a while we assess whether to add a dedicated line. The list updates without any manual step — the client syncs the latest routes when you sign in, and Announcements covers recent changes.

Routes Ready to Go

Signing up takes only a username and password — no email address; plans start at ¥9.9/month, with unlimited devices and a 14-day money-back guarantee. Pick your direction and slot the route into your day.

Start Free View Plans