Route list

Server locations and route types

C6VPN currently offers 110+ countries and 250+ international routes, grouped into four regions: Asia-Pacific, North America, Europe and Other. The table below shows a selection of cities and route types; the full node list is grouped by region inside the client. A single city may offer several route types at once, and switching nodes does not require re-importing the subscription.

  • 110+ countries
  • 250+ routes
  • Unlimited devices online at once
  • 30-day money-back guarantee
  • Japan
  • United States
  • Hong Kong
  • Singapore
  • United Kingdom
  • South Korea
  • Germany
  • Australia
  • France
  • Netherlands
  • Thailand
Grouped by region

Route list by region

The table below groups a selection of cities into four regions — Asia-Pacific, North America, Europe and Other — and lists route types and streaming support. The route-type badges are explained in the next section. Supported means the city's routes work with major streaming platforms; Partial means only some platforms do. The labels inside the client are the final reference.

Country / RegionCityRoute typeStreaming
Asia-Pacific
Japan Tokyo IEPL Supported
Japan Osaka Relay Supported
Hong Kong Hong Kong Direct Supported
Singapore Singapore IEPL Supported
South Korea Seoul Direct Supported
South Korea Busan Relay Partial
Australia Sydney IEPL Supported
Australia Melbourne Relay Partial
North America
United States Los Angeles Relay Supported
United States San Jose Direct Supported
United States Seattle Relay Supported
United States New York IEPL Supported
United States Dallas Direct Partial
Europe
United Kingdom London Relay Supported
United Kingdom Manchester Direct Partial
Germany Frankfurt Relay Supported
Germany Berlin Direct Partial
Germany Munich IEPL Supported
Other
France Paris Relay Supported
Netherlands Amsterdam IEPL Supported
Thailand Bangkok Direct Partial
Notes

The table is a sample, not all 250+ routes. Inside the client, the node list is grouped by region and purpose, and every route is labelled with its type. Routes change with operating conditions, so the list actually available in the client is the reference.

One subscription works on unlimited devices, and each device picks its own node without affecting the others. The node list syncs when the subscription updates; if a route in use is changed, the client prompts you to pick another one.

Route types

How the three route types differ

A route type describes how data travels from entry to exit, not which country the node sits in. The client labels each node with its type, and one city may offer several paths at once. Understanding the difference between the three matters more than counting nodes.

IEPL

IEPL dedicated

Traffic runs from entry to exit over a layer-2 dedicated line from the carrier, skipping the public internet on the international leg, so the path is fixed and jitter stays low. The trade-off is that bandwidth is billed as a dedicated line, which makes it the most expensive per unit, so it is usually deployed only in core cities and popular exits.

Data path
Entry → dedicated line → exit, with a fixed path end to end.
Best for
Long online meetings, long-lived AI tool sessions, 4K video, large downloads.
Cost difference
Highest of the three; deployed mainly in core cities.
Relay

Relay route

The client first connects to a relay node near the user, which then hands off to the exit, using a better-quality path to avoid a volatile international leg. It adds one hop, the path varies with the relay node, and the cost sits in the middle.

Data path
Entry → relay node → exit, with one extra hop.
Best for
Distant regions where direct connections fluctuate, such as Europe and the US East Coast.
Cost difference
Mid-range; covers more cities than dedicated lines.
Direct

Direct route

The client connects straight to the exit node with no relay in between. Simplest structure, shortest path, lowest cost; the trade-off is no extra protection on the international leg, so congestion hits sooner over long distances.

Data path
Entry → exit, connected directly.
Best for
Nearby regions such as Hong Kong, Seoul, Tokyo and Singapore.
Cost difference
Lowest; covers the most cities.
Route typeData pathBest forRelative cost
IEPL dedicatedEntry reaches the exit over a carrier dedicated line, skipping the public internet on the international legLong meetings, AI tools, 4K video, large file transfersHighest
RelayEntry connects to a nearby relay node first, then hands off to the exitDistant regions where direct connections fluctuateMid-range
DirectThe client connects straight to the exit node with no extra relayNearby regions; scenarios sensitive to round tripsLowest
By use case

Choosing a route by use case

One subscription works on unlimited devices, and each device picks its own node. Below are starting points for five common use cases; what you see in the client is the real reference, and you don't have to commit to one choice — you can switch routes at any time without affecting other devices.

Everyday browsing and research

Pages, search and email are short requests with many round trips, so the closer the exit, the shorter the wait. Start with direct routes in Hong Kong, Tokyo and Seoul; when the international leg fluctuates, switch to a dedicated route in the same city.

  • Hong Kong direct
  • Tokyo direct

Video and streaming

4K has a high bitrate and long playback sessions, so what matters is sustained bandwidth rather than peak speed. Prefer dedicated routes in Tokyo and Singapore; for US content, use the Los Angeles relay or the New York dedicated route. If playback keeps buffering, switch to another route in the same region first.

  • Tokyo IEPL
  • Singapore IEPL
  • Los Angeles relay

AI tools

AI services are sensitive to consistency between the exit region and the account region, so pick one route and don't switch often. Prefer dedicated routes in the United States, Japan and Singapore; long conversations and code completion are long-lived connections where drops hurt more than speed.

  • New York IEPL
  • Tokyo IEPL
  • Singapore IEPL

Gaming and real-time matches

Competitive games care about round trips and jitter, not bandwidth. Prefer direct routes in Hong Kong, Seoul and Tokyo — the shorter the path the better. For cross-region play, pick an exit in the game server's region rather than the one closest to you.

  • Hong Kong direct
  • Seoul direct

Work and remote meetings

Meetings are a sustained uplink, so jitter affects the experience more than peak speed. Prefer an exit in the region where your company's services run, and choose a dedicated route. When several people are online at once, having each pick a node in a different city avoids queueing on the same path.

  • Frankfurt relay
  • Munich IEPL
  • Sydney IEPL

Switching routes happens on the client home screen: the node list is grouped by region, and a tap switches you over — no need to re-import the subscription. To understand how routes and regions relate, see How to choose a route: region, route type and use case; if you run into problems while connected, check Troubleshooting first, then open a ticket from the contact page.

FAQ

Route selection FAQ

Five common questions about node counts, route types and switching.

Why does the table list fewer routes than 250+?

The table is a sample that shows how regions and route types are distributed, not the full list. All 250+ routes are grouped by region inside the client and change with operating conditions; the numbers on this page and the list in the client refer to the same set of routes.

Do I need to re-import the subscription to change cities?

No. It is the same subscription; the node list syncs from it and you switch by tapping inside the client. Multiple devices each pick their own node without affecting the others, and there is no limit on devices online at once.

Is an IEPL dedicated route always faster than a relay?

Not always. The advantage of a dedicated line is a fixed path and low jitter, which suits long sessions; if entry and exit are already close, a direct route has fewer round trips and may feel better. When choosing, look at distance first, then route type.

What does Partial mean in the streaming column?

It means the city's routes work with some streaming platforms, not all of them. Platform risk controls and region checks change, so the labels in the client and actual playback are the reference; if playback fails, try another route in the same region.

Do routes change often?

Yes. Routes are added and removed, types change and cities expand with operating conditions, and the list in the client syncs after a subscription update. What this page shows is part of the current offering; the pricing page and refund policy are the reference for terms that stay in force.

The route list is grouped by region inside the client. No email address is required to create an account — a username and password are enough. Monthly plans start at ¥9.9 with 60GB, devices online at once are unlimited, and there is a 30-day money-back guarantee.

Get Started Free