120+countries and regions
Exits in Asia Pacific, North America, Europe and other regions, with 220+ routes in total.
120+ countries / 220+ routes
Server locations and route coverage
Common routes are grouped into four regions — Asia Pacific, North America, Europe and others — with notes on how IEPL, relay and direct connections work, what they cost and where they fit. The table keeps only stable, static information; route types and cities change as coverage expands.
- Quantum encryption
- 14-day money-back guarantee
- Unlimited devices
- No email address required
220+to choose from
A single city may offer dedicated, relay and direct routes at once — pick by use case.
14day money-back guarantee
Unlimited devices; Alipay, WeChat Pay and USDT accepted.
Route list
Common routes in four regions
The table below is a sample of common routes, grouped into Asia Pacific, North America, Europe and other regions. The country/region column is where the exit sits, the city column is the data center you connect to, the route type column explains how that route is provisioned, and the streaming column notes which content library that exit region can reach. The full list expands by region inside the app, covering 120+ countries and 220+ routes.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Asia Pacific | |||
| Japan | Tokyo | IEPL dedicated | Japan catalog / anime |
| Japan | Osaka | Relay | Japan streaming |
| Hong Kong | Hong Kong | IEPL dedicated | Hong Kong & Southeast Asia |
| Singapore | Singapore | IEPL dedicated | Southeast Asia |
| South Korea | Seoul | Relay | Korea catalog |
| Malaysia | Kuala Lumpur | Direct | Southeast Asia |
| Australia | Sydney | Direct | Australia streaming |
| North America | |||
| United States | Los Angeles | IEPL dedicated | Major US streaming |
| United States | San Jose | Relay | Major US streaming |
| United States | Seattle | Direct | US streaming |
| Canada | Toronto | Relay | Canada streaming |
| Canada | Vancouver | Direct | Canada streaming |
| Europe | |||
| United Kingdom | London | IEPL dedicated | UK streaming |
| Netherlands | Amsterdam | IEPL dedicated | Major European streaming |
| Germany | Frankfurt | Relay | Major European streaming |
| Switzerland | Zurich | Relay | Major European streaming |
| France | Paris | Direct | France streaming |
| Other | |||
| United Arab Emirates | Dubai | Relay | Middle East |
| Turkey | Istanbul | Relay | Europe / Middle East crossroads |
| India | Mumbai | Direct | South Asia |
| Brazil | São Paulo | Direct | South America |
The table deliberately omits latency and load figures. Both shift with your local carrier, time of day and routing, so a fixed number on a page tells you nothing; check the live route status in the app after connecting. When choosing, run real traffic through two or three routes in the same region before settling on one for the long term.
Route type
Dedicated, relay and direct: how they differ
All three connection types solve the same problem: keeping the cross-border leg within an acceptable range of uncertainty. What differs is who maintains the path, where the cost sits and what each one is best at.
A separate channel for the cross-border leg
IEPL (International Ethernet Private Line) gives the cross-border leg its own Layer 2 channel, so that traffic never competes for bandwidth with public internet exits. Ordinary exits see packet loss and jitter at peak hours; on a dedicated segment bandwidth is reserved by contract, so the latency curve is flatter and jitter lower. The trade-off is the highest cost per unit of bandwidth, which is why it is deployed only in the busiest cities: Tokyo, Hong Kong, Singapore, Los Angeles, London and Amsterdam. It suits long video calls, cross-border work and 4K streaming at peak hours — anything that needs continuity.
- Fixed cross-border path, the least variation at peak hours
- Highest relative cost, narrowest city coverage
Nearby entry point plus optimized routing
Relay routes first bring traffic into an entry data center near you, then forward it to the exit over a pre-tuned path. That pulls the uncertainty of the last mile into the entry node, and the cross-border leg runs over maintained routing instead of leaving it to chance. Cost sits in the middle, city coverage is the widest, and it is the default choice for most people. It suits everyday browsing, AI tools and streaming, and local connections whose international exit quality is only average.
- Widest city coverage, plenty of options
- Performance depends on the link from the entry data center to your network
Exit data center peers directly with local carriers
Direct routes peer the exit data center straight with local carriers: shortest path, simplest structure, lowest cost. Performance depends more on the path from your network to that data center — solid within the same city or region, more variable across continents. Use them as backup, or for services that don't care about the path: file sync, software updates, static pages. Keeping an extra direct route in the same region means you don't have to change regions when a dedicated line is being adjusted.
- Shortest path, lowest relative cost
- More noticeable variation on intercontinental access
| Item | IEPL dedicated line | Relay | Direct |
|---|---|---|---|
| Cross-border path | Dedicated Layer 2 channel | Forwarded via nearby entry | Exit peers with carrier |
| Peak-hour behavior | Least variation | Fairly stable | Noticeable variation |
| Relative cost | Highest | Mid-range | Lowest |
| Typical cities | Tokyo / Hong Kong / Los Angeles | Seoul / Frankfurt | Sydney / Paris / Mumbai |
| Best for | Meetings / work / 4K | Browsing / AI / streaming | Backup / sync / updates |
Switching doesn't affect your subscription: the three types are not replacements for one another. One account can move between routes in the app; if a route underperforms, switch to another in the same region — the subscription you already imported needs no reconfiguration.
Choosing a route
Pick a route by use case
A single city often has several routes with different connection types. Work out what your use case needs in latency, jitter and bandwidth first, then choose — that saves more time than working through the whole table.
The nearest relay is the least fuss
Web pages, email and social apps don't need much bandwidth but are sensitive to time to first byte. Pick the geographically closest entry and let a relay handle the cross-border leg — usually snappier than a direct route across continents. If your city has a dedicated-line entry and budget allows, go dedicated first.
RelayDirect
Dedicated first, then the region
4K streaming needs sustained bandwidth, not peak bursts. For Japanese or US content, choose a dedicated line in that region; where a platform checks exit region strictly, stick to one route instead of switching often, which cuts re-logins and risk-control flags.
IEPL dedicatedJapan / US
A stable exit matters more than peak speed
AI tools care about session continuity. Choose a relay route and stay on the same exit region so a mid-session switch doesn't break the conversation; for long chats or large uploads, prefer a dedicated line with reserved bandwidth to avoid retries.
RelayFixed exit
Jitter matters more than bandwidth
Online games are sensitive to jitter and not very demanding on bandwidth. Prefer a dedicated line in the same region to keep the path fixed; when playing across continents, an optimized relay route is usually steadier than a direct one and holds a long session without dropping.
IEPL dedicatedSame region
A fixed exit is easier to manage
Business email and internal systems often whitelist by exit address. Give work devices a fixed dedicated or relay route so the exit never changes and repeated verification drops; for video meetings, prefer a dedicated line to keep upstream steady.
IEPL dedicatedRelay
Coverage
Exits in 120+ countries and regions
Below are the countries and regions where common exits sit. The full list, grouped by region, expands inside the app; for which connection types a given city offers, the route list in the app is authoritative.
- United States
- Japan
- Singapore
- Hong Kong
- South Korea
- Australia
- United Kingdom
- Germany
- Netherlands
- Switzerland
- Canada
- United Arab Emirates
120+ countries and regions and 220+ routes is the coverage currently on sale. Common exits cluster in Asia Pacific, North America and Europe; other regions lean on relay and direct routes. Both the table and the badge wall show static information only — once connected, the route status in the app is what counts.
FAQ
Route FAQ
How is the 220+ route count calculated?
It counts selectable routes, where one route is a city plus a connection type. Coverage spans 120+ countries and regions, and a single city may offer dedicated, relay and direct at once, so routes outnumber cities.
Why are there no latency or load figures in the table?
Latency shifts with your local carrier, time of day and routing, so a fixed number means little; a load percentage can't be kept accurate from a static page either. Check the live route status in the app after connecting and trust what you measure on your own network.
What makes a dedicated line more expensive than a relay?
The cross-border bandwidth is reserved, so it doesn't compete with public traffic on international exits. The gap shows most at peak hours, when dedicated lines see less packet loss and jitter. The trade-off is a higher cost per unit of bandwidth, which is why they only run in the busiest cities.
What if a route won't connect?
Switch to another route in the same region first; if every route there misbehaves, move to a nearby region. If it still fails, check your local network and app version, then open a ticket in the user panel with your city and the route type you were using.
Do routes change often?
Cities and connection types in the table are updated whenever capacity or data centers change. Existing plans are unaffected — refresh your subscription in the app to see the latest route list.
What does the streaming column mean?
It means the region that exit sits in can reach the main local content libraries; actual availability depends on the platform's own regional policy and how it judges you at the time. For services that check region strictly, stay on one fixed route and switch less.
To see prices and data packs first, go to Plans & Pricing; if this is your first time, start with the Guides.