110+ countries and 190+ routes are listed by group — Asia-Pacific, North America, Europe and others — with every route tagged by type (direct / relay / dedicated) and streaming support. Below you'll find notes on each route type, a use-case order for picking one, and how to confirm your exit after switching. The table shows representative routes only; the full list expands by region inside the client.
The table lists representative routes only; the same city may have several routes of different types. The full list and live route status are in the client; new regions arrive with client config updates, so no reinstall is needed.
Asia-Pacific routes
01
The closest group, with a short cross-border hop — suited to everyday browsing, Japan and Hong Kong streaming, and office work that needs a low hop count. Japan, Hong Kong and Singapore each offer both dedicated and relay routes, and one city often has several to choose from.
Sample routes in Asia-Pacific
Country / Region
City
Route type
Streaming
Japan
Tokyo
Dedicated
Supported
Japan
Osaka
Direct
Supported
South Korea
Seoul
Direct
Supported
Singapore
Singapore
Dedicated
Supported
Hong Kong, China
Hong Kong
Relay
Supported
Taiwan, China
Taipei
Direct
Partial
Malaysia
Kuala Lumpur
Relay
Partial
Thailand
Bangkok
Relay
Partial
Australia
Sydney
Direct
Supported
North America routes
02
Covers the US West and East coasts plus major Canadian cities. AI tools, developer docs and North American streaming mostly land in this group; West Coast routes have a shorter return path toward Asia, while East Coast routes suit services in the eastern US and Europe.
Sample routes in North America
Country / Region
City
Route type
Streaming
United States
Los Angeles
Dedicated
Supported
United States
San Jose
Direct
Supported
United States
New York
Relay
Supported
Canada
Toronto
Direct
Supported
Canada
Vancouver
Relay
Supported
Mexico
Mexico City
Relay
Partial
Europe routes
03
London, Frankfurt, Amsterdam, Zurich and other cities make up the Europe group — suited to European streaming, cross-border work and sign-ups that need a European exit. The group is mostly direct and relay routes, with dedicated routes in London and Zurich.
Sample routes in Europe
Country / Region
City
Route type
Streaming
United Kingdom
London
Dedicated
Supported
Germany
Frankfurt
Direct
Supported
Netherlands
Amsterdam
Relay
Supported
France
Paris
Direct
Supported
Switzerland
Zurich
Dedicated
Supported
Sweden
Stockholm
Direct
Partial
Spain
Madrid
Relay
Partial
Poland
Warsaw
Relay
Partial
Other regions
04
Selected cities in the Middle East, South America, Africa and Oceania. This group has fewer routes than the first three and is mostly relay and direct — suited to single-purpose needs that require a local exit; if you just want to reach international sites, pick from the first three groups.
Sample routes in other regions
Country / Region
City
Route type
Streaming
United Arab Emirates
Dubai
Relay
Partial
Turkey
Istanbul
Relay
Partial
Israel
Tel Aviv
Relay
Partial
Brazil
São Paulo
Direct
Partial
South Africa
Johannesburg
Relay
Partial
Indonesia
Jakarta
Direct
Partial
New Zealand
Auckland
Direct
Partial
Route type
How the three route types differ
Route type decides which path your data takes from your device to the target site. On the same cross-border link, direct, relay and dedicated routes differ in path length, congestion risk and cost — and each suits different work. Below are the mechanics, the best-fit scenarios and the cost differences, followed by a comparison table.
01
Direct routes
How it works
The client connects to the nearest entry data center and goes out directly, with no extra forwarding node in between. Shortest path, fewest hops.
Best for
Everyday browsing, long-term use in a single region, latency-sensitive web work.
Cost
The lowest of the three, and the largest number of routes — a single city usually has several to choose from.
Watch out
Performance depends on the local-to-entry segment, which is more exposed to local egress congestion at peak hours.
02
Relay routes
How it works
Traffic first reaches a nearby relay entry, then a relay data center forwards it to the exit node — splitting local-to-exit into two segments, with the first running over an optimized link.
Best for
Mediocre local egress quality with clear peak-hour swings; needing several regions from one client.
Cost
Medium — one extra forwarding hop of resources over direct, with a route count between direct and dedicated.
Watch out
One more forward, so theoretical latency is slightly higher than direct, but stability is usually better.
03
Dedicated routes
How it works
The cross-border segment runs on a dedicated or semi-dedicated link from the data center (IEPL and similar), so it does not compete for the same egress as public traffic; bandwidth and routing are relatively fixed.
Best for
Long video meetings, large file transfers, high-bitrate streaming, jitter-sensitive real-time work.
Cost
The highest of the three — bandwidth costs more than direct or relay, so dedicated routes are fewer than direct ones.
Watch out
Dedicated routes solve the cross-border segment; local network quality is still a prerequisite.
Route types compared
Route type
Cross-border path
Latency profile
Stability
Best for
Relative cost
Direct
Direct exit from the entry data center
Shortest path, heavily affected by local egress
Fair
Everyday browsing, single-region use
Low
Relay
Forwarded via a nearby relay entry
One hop more than direct, less variation
Good
Multi-region switching, peak hours
Medium
Dedicated
Dedicated or semi-dedicated cross-border link
Fixed path, minimal jitter
Very good
Meetings, large files, high-bitrate playback
High
The latency profile describes path structure, not specific numbers; real performance depends on your local network, the target service and the time of day.
Choosing a route
Pick a route by use case
A three-step order works: pick the region by target service, then the route type by use case, then rotate-test among several routes in the same region. Below are concrete orders for five common use cases.
Everyday browsing
Direct first
Web pages, search and email are latency-sensitive but not bandwidth-hungry, so a short direct path fits better. Start with the closest city in the Asia-Pacific group — Japan, Hong Kong and Singapore all have several routes.
Order same-city direct → same-city relay → nearby city
Video and streaming
Dedicated first
High-bitrate playback suffers from jitter and packet loss, not peak bandwidth. Confirm which region the content comes from, then pick a dedicated route in that region; if the bitrate drops mid-play, switch to another route in the same region rather than jumping across regions.
Order dedicated in target region → relay in same region → direct in same region
AI tools
North America first
Conversational tools hold long connections, so a dropped stream hurts more than slowness. Pick a dedicated or direct route on the US West or East Coast and stay on it; if verification breaks, retry on another route in the same region first.
Order US West dedicated → US East dedicated → US West direct
Gaming
Fewest hops first
Games are the most sensitive to latency and jitter, and need little bandwidth. Pick a route in the same region as the game server, direct first; don't switch routes mid-match, since switching rebuilds the connection.
Order same-region direct → same-region dedicated → nearby-region direct
Work and meetings
Dedicated first
Video meetings are sustained two-way traffic and sensitive to packet loss. Fix one dedicated route before the meeting and pause large downloads on the same network; if the picture stutters, check the current route type first, then decide whether to move to another dedicated route in the same region.
Order same-region dedicated → same-region relay → change entry city
Try it first, then pick a route by use case
Monthly plans start at ¥9.9 for 60GB, ¥18/month for 250GB and ¥28/month for 500GB, with data resetting monthly on your activation date; data packs start at ¥158/300GB, last until used up and never expire. No email address needed — a username and password are enough — and there's a 60-day money-back guarantee.
Below are some of the covered countries and regions, grouped by continent, to help you judge roughly which group a target service falls into. The full list lives in the client's region list; new regions arrive with client config updates.
Asia-Pacific
Japan
South Korea
Singapore
Hong Kong, China
Taiwan, China
Malaysia
Thailand
Vietnam
Philippines
Indonesia
India
Australia
New Zealand
North America
United States
Canada
Mexico
Europe
United Kingdom
Germany
Netherlands
France
Switzerland
Sweden
Norway
Denmark
Finland
Spain
Italy
Poland
Czechia
Austria
Ireland
Middle East & Africa
United Arab Emirates
Turkey
Israel
Saudi Arabia
South Africa
Egypt
Nigeria
South America
Brazil
Argentina
Chile
Colombia
Peru
Switching and verifying
Confirm the exit region after switching
Switching routes doesn't mean you're already on the expected exit. Run these four checks to tell whether the problem is the route, the region or your local network.
Pick a region and route in the client
The route list is grouped by region and each route is labelled with its type. When a city has several routes, pick the type by use case first, then choose one route of that type.
Check the exit region after connecting
Open the network check page and confirm the exit country matches the region you picked. If it doesn't, the connection isn't on the expected route — stop there before troubleshooting further.
If it doesn't match, change route first, then region
Change one variable at a time: try another route in the same region first, and only change region if it's still wrong. That tells you whether the route or the region is the problem.
Check streaming content separately
Platforms decide the content library by exit region. If the exit is right but the library isn't, try another route in the same region; switching across regions restarts the check.
110+ countries and 190+ routes. The table on this page lists representative routes only; the full list expands by region in the client, and new regions arrive with client config updates.
Are dedicated routes always faster than direct ones?
Not necessarily. Dedicated routes improve stability and jitter on the cross-border segment; if the local-to-entry segment is poor, every route is affected. Test a direct route first, then compare with a dedicated route in the same city, rather than judging by route type alone.
Do I pay extra to switch routes?
No. All routes in your plan can be switched freely, and data resets monthly on your activation date; if you upgrade mid-cycle, the price difference is prorated over the remaining days.
What does "Partial" mean in the streaming column?
It means routes in that region can reach the content library of some platforms, and the result changes with the platform's current region checks. If the exit is right but the library isn't, try another route in the same region rather than jumping across regions.
Is there a limit on simultaneous devices?
No device limit. Each device can pick its own route independently; using different regions on different devices with the same account needs no extra setup.
Can I get a refund if it's not for me?
There's a 60-day money-back guarantee — see the refund policy for the steps. No email address is needed to get started; a username and password are enough.