110+ countries / 250+ routes

Global route list: 110+ countries / 250+ routes

110+ countries and 250+ routes grouped by Asia-Pacific, North America, Europe and other regions, each one tagged with its route type and streaming support. Route types fall into three groups — IEPL, relay and direct. How each one works, where it fits and how the costs differ is covered below.

Start Free View Plans
  • No logs
  • 60-day refund
  • Unlimited devices
  • Alipay · WeChat Pay · USDT

ROUTE TABLE

A route list grouped by region

The table below lists representative routes by region across four groups — Asia-Pacific, North America, Europe and other — with country, city, route type and streaming support for each. The route type decides which path the cross-border leg takes and directly shapes how the route behaves at peak hours, so it is worth reading before the city name.

The table holds static information only, with no latency or load figures. Latency shifts with your local network, your carrier and the time of day, and the same node can measure several times apart at different hours; hard-coding a number on the page would only mislead. For current status, go by the route list inside the client.

Country City Route type Streaming support
Asia-Pacific
Hong Kong, ChinaHong KongIEPLNetflix / YouTube
JapanTokyoIEPLNetflix / Disney+
JapanOsakaRelayYouTube 4K
SingaporeSingaporeRelayNetflix
South KoreaSeoulRelayNetflix / Disney+
Taiwan, ChinaTaipeiRelayYouTube
MalaysiaKuala LumpurDirectYouTube
ThailandBangkokDirectNetflix
VietnamHo Chi Minh CityDirectYouTube
IndonesiaJakartaDirectYouTube
IndiaMumbaiRelayNetflix
AustraliaSydneyRelayNetflix / Disney+
New ZealandAucklandDirectYouTube
North America
United StatesLos AngelesDirectYouTube 4K
United StatesSan JoseIEPLNetflix / Disney+
United StatesSeattleRelayNetflix
United StatesNew YorkRelayNetflix / HBO Max
United StatesDallasDirectYouTube
United StatesChicagoRelayNetflix
CanadaTorontoRelayNetflix
CanadaVancouverDirectYouTube 4K
Europe
United KingdomLondonRelayNetflix / BBC iPlayer
GermanyFrankfurtRelayDisney+
GermanyBerlinDirectYouTube
FranceParisRelayNetflix
NetherlandsAmsterdamIEPLNetflix
ItalyMilanDirectNetflix
SpainMadridDirectNetflix
SwedenStockholmDirectYouTube
SwitzerlandZurichRelayNetflix
PolandWarsawDirectYouTube
Other
United Arab EmiratesDubaiRelayNetflix
IsraelTel AvivDirectYouTube
TürkiyeIstanbulDirectNetflix
South AfricaJohannesburgDirectYouTube
BrazilSão PauloRelayNetflix
ArgentinaBuenos AiresDirectYouTube
MexicoMexico CityDirectNetflix

The table is an excerpt showing representative routes per region; the full list sits inside the client, grouped by region and updated as routes change. A single city can carry several routes of different types at once, so go by the live list in the client.

LINE TYPES

Route types explained

A route type describes how traffic travels from the entry point to the exit. The three types differ clearly in how they work, what they cost and where they fit; sorting those three things out first saves more time than repeatedly testing nodes. A name with “dedicated” in it is not automatically right for every use, and the cheapest direct route is not only good as a fallback.

  • IEPL

    Highest cost
    How it works
    An International Ethernet Private Line builds a point-to-point Layer 2 channel between the entry point and the exit. The cross-border leg does not pass through public internet gateways and does not compete with other users for the same slice of bandwidth.
    Where it fits
    Cross-border work, video meetings, sustained calls to AI tools, and long sessions that are sensitive to jitter. For anything that has to stay connected for hours, pick this type first.
    Cost difference
    The most expensive of the three. Bandwidth is procured at a clearly higher unit price than relay or direct, so IEPL routes are fewer in number and are usually deployed in the most popular regions first.

  • Relay

    Mid cost
    How it works
    The client connects to a relay node first, and that relay node forwards traffic on to the exit node. The cross-border leg runs over a high-quality link at the relay's location, while the exit leg runs over the local network — effectively swapping the longest stretch for a steadier one.
    Where it fits
    Everyday browsing, streaming, and any use that needs long-term stability on a limited budget. Relay is the most numerous route type and covers the widest range of regions.
    Cost difference
    Mid-range. Relay nodes are shared between users, so peak-hour behaviour depends on node capacity and scheduling — which is why two routes in the same city can perform differently.

  • Direct

    Lowest cost
    How it works
    The client connects straight to the exit node with no extra relay hop, so the path is the shortest and the setup is the simplest. The cross-border leg goes out through public internet gateways and does not occupy dedicated capacity.
    Where it fits
    Nearby access, short-term use, one-off latency-sensitive actions, and as a backup for IEPL and relay routes. There are many of them spread across many regions, which makes them a good fallback.
    Cost difference
    The cheapest. Because the cross-border leg uses public internet gateways, it feels peak-hour congestion on shared links more noticeably, so it is not the best fit for long sessions that demand maximum stability.

LINE PICKING

Picking a route by use case

One region often carries all three types at once — IEPL, relay and direct. Picking is not about choosing the most expensive name; it starts with the use case: long connections care about stability, short requests care about path length, playback cares about spare bandwidth. Below are priorities and things to check for five common use cases.

Everyday browsing and search

First choice: relay / direct

Web pages and search requests are mostly short connections, where a short path and a fast handshake matter more than peak bandwidth. Prefer a nearby relay node or a direct node, and keep browser traffic separate from system updates and cloud drive sync so you avoid unnecessary detours and bandwidth use.

Streaming

First choice: IEPL / relay

Which regional library you can reach is decided by where the exit node sits, not by the route type. 4K playback is more sensitive to sustained bandwidth, so pick an IEPL route or a high-quality relay with more headroom, and stay on the same route throughout — switching mid-playback only triggers another round of buffering.

AI tool calls

First choice: IEPL

Chat and content-generation requests are mostly long connections, more sensitive to link stability and packet loss, and a single drop means starting over. Prefer IEPL; where a region has none, choose a relay node with fewer users and keep the same route for the whole session.

Online gaming

First choice: IEPL / direct

Games care about latency jitter rather than peak bandwidth. Avoid paths that hop through several forwarders, prefer a node in the same region as the game server or a neighbouring one, and turn off background sync and auto-updates so downloads do not take over the link.

Cross-border work

First choice: IEPL

Video meetings and file sync put more demands on upstream stability. Pick one IEPL route and stay on it long term, and route meetings, email and document services through the same exit — that cuts down on repeated verification caused by a changing IP and makes problems easier to trace.

PROTOCOLS & CLIENTS

Protocols and clients

The protocol decides how data is wrapped and carried between client and node. One device can run several clients at once, and each protocol leans a different way on compatibility, overhead and weak-network behaviour; if you are unsure, start with the default and switch only if something goes wrong.

Protocol support

Every route supports the protocols below and you can switch between them inside the client without re-importing the subscription.

  • TrojanDisguised as ordinary HTTPS traffic, widely compatible, and a good fit for everyday use that needs stability.
  • VLESSLight handshake overhead and a lean implementation — the most common protocol on relay and direct routes.
  • Hysteria2Built on QUIC, it holds up comparatively well under high packet loss and weak networks.
  • ShadowsocksThe most compatible option, and it runs directly on routers and older devices.
  • VMessWorks with older clients and is worth keeping as a backup profile.
  • TUICAlso a QUIC-family protocol, serving as a backup for Hysteria2.

Clients

Clients cover Windows, macOS, iOS, Android and Linux, and one account can be online on unlimited devices at the same time. Installers and subscription links are all inside the user panel and available once you log in; no email address is needed — a username and password are enough.

  • Windows
  • macOS
  • iOS
  • Android
  • Linux
Get the clients Import steps

COVERAGE

Regions covered

110+ countries and 250+ routes are filed by region, and each region below has several cities with exits. Cities inside one region can back each other up: when your main route wobbles, switching to another city in the same region is usually steadier than jumping across regions.

  • Asia-Pacific

    Hong Kong · Tokyo · Osaka · Seoul · Singapore · Taipei · Kuala Lumpur · Bangkok · Sydney · Auckland

  • North America

    Los Angeles · San Jose · Seattle · New York · Dallas · Chicago · Toronto · Vancouver · Mexico City

  • Europe

    London · Frankfurt · Berlin · Paris · Amsterdam · Milan · Madrid · Stockholm · Zurich · Warsaw

  • Middle East & Africa

    Dubai · Tel Aviv · Istanbul · Johannesburg

  • South America

    São Paulo · Buenos Aires · Santiago

FAQ

Route questions

Five frequent questions about route types, device counts and billing cycles, answered only from what the terms of service already state.

Why are there no latency figures in the route list?

Latency shifts with your local network, your carrier and the time of day, and the same node can measure several times apart at different hours; hard-coding a number on the page would only mislead. This page lists static facts only: region, city, route type and streaming support. For current status, go by the route list inside the client.

What makes IEPL more expensive than relay?

An IEPL builds a point-to-point channel between the entry point and the exit, so the cross-border leg does not pass through public internet gateways and does not share the same slice of bandwidth with other users — which is why it costs more to procure. Relay and direct routes share public links, cost less, and are more exposed to overall link congestion at peak hours. The two types fit different uses; it is not simply a matter of expensive versus cheap.

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

Unlimited. Windows, macOS, iOS, Android and Linux can all be online at once, and one account does not need a separate purchase per device. If you have many devices, it helps to assign routes by use case rather than crowding them all onto a single route.

What if I pick the wrong route — can I switch any time?

Yes. Routes are switched inside the client without re-importing the subscription; connections opened after the switch take the new route, and transfers already in progress are best left to finish first. It is worth settling on two or three routes per use case: one primary and one backup in the same region, ready to switch when things wobble.

When does data reset?

On a monthly plan, data resets every month from the activation date rather than on the first of the calendar month; if you upgrade mid-cycle, the difference is converted into the remaining days. Data packs last until they run out and never expire, which suits usage that varies from month to month.

A route that will not connect, a subscription that fails to import, an app that ignores the proxy — these troubleshooting steps are collected in the troubleshooting handbook, with a chapter per symptom covering how to diagnose and check things yourself; per-platform import steps are in the getting started guide.

Check the route list first, then pick a plan

No email address needed — a username and password are enough; unlimited devices, 60-day refund.

Start Free