Server Locations - 23VPN | Global Routes and How to Choose

$ nodes.list --group region

Regional Routes at a Glance

The table illustrates coverage directions and entry-point types; it is not a complete server list. Routes may change with network conditions and platform policies. Before connecting, choose a region based on the target service, then verify the actual result in the client.

INFO

“Supported” means the entry point is configured for access to the relevant streaming services. “Some platforms” means regional detection may vary between content services. Account region, content rights, and payment region remain determined by the respective platform.

Go to route selection →

Country / Region	City	Route type	Streaming support
Asia-Pacific
Hong Kong, China	Hong Kong	IEPL	Supported
Singapore	Singapore	IEPL	Supported
Japan	Tokyo	IEPL	Supported
Japan	Osaka	Relay	Some platforms
Taiwan, China	Taipei	Relay	Supported
South Korea	Seoul	Relay	Some platforms
Malaysia	Kuala Lumpur	Direct	Some platforms
Thailand	Bangkok	Direct	Some platforms
Indonesia	Jakarta	Direct	Some platforms
North America
United States	Los Angeles	IEPL	Supported
United States	Seattle	Relay	Supported
Canada	Toronto	Direct	Some platforms
Mexico	Mexico City	Direct	Some platforms
Europe
United Kingdom	London	IEPL	Supported
Germany	Frankfurt	Relay	Supported
Netherlands	Amsterdam	IEPL	Supported
France	Paris	Direct	Some platforms
Switzerland	Zurich	Direct	Some platforms
Sweden	Stockholm	Direct	Some platforms
Other regions
Australia	Sydney	Relay	Supported
New Zealand	Auckland	Direct	Some platforms
Brazil	São Paulo	Direct	Some platforms
United Arab Emirates	Dubai	Direct	Some platforms
South Africa	Johannesburg	Direct	Some platforms

$ man route-types

How to read route types

IEPL, relay, and direct connections are not simply higher or lower tiers. They use different entry and forwarding methods, balancing stability, coverage, scheduling flexibility, and operating cost in different ways.

--iepl managed path

IEPL

IEPL places the cross-border connection on a more controlled transport path and is generally suited to continuous sessions, video calls, and large file transfers. Its purpose is not to promise a fixed speed figure, but to reduce disruption from changing public-network paths and make connection behavior more consistent.

These routes require more network resources and ongoing scheduling, so they are usually prioritized in regions with concentrated demand. They suit long periods of remote work, frequent use of international collaboration tools, high-resolution streaming, or users who prefer fewer manual switches. If the target service has an IEPL entry point in its region, start by testing that route.

--relay balanced path

Relay routes

A relay route first connects to a nearby entry point, then the service selects a subsequent path to the target region. This can avoid some unstable public-network paths and makes it easier to adjust the exit for different access networks. The benefit is scheduling flexibility: the entry and exit can be optimized separately instead of making the user take on the entire long-distance path directly.

Relay routes suit everyday browsing, AI tools, streaming, and general office work, and are often a practical compromise for reaching more distant regions. Operating costs generally fall between IEPL and direct connections. When a city has multiple relay entry points, do not judge by name alone; connect and check the target service’s response and continuity.

--direct wide coverage

Direct connections

A direct route connects from the current network straight to a server in the target region. Its path is simple and can bring more regions into the coverage directory. It suits clearly defined tasks to nearby targets with suitable local interconnection, as well as temporary region switching, checking a page’s regional version, or work that does not require strong continuity.

Direct connections depend more heavily on the local provider and the current state of international routing, so differences between access environments can be more noticeable. Their resource structure is relatively straightforward, coverage is flexible to expand, and costs are generally easier to control. Choose a geographically nearby target region first, while keeping relay or IEPL routes as alternatives.

ROUTE COST MODEL

Cost differences come from how routes are organized

IEPL requires reserving and maintaining more controlled cross-border capacity; relay routes require managing the entry point, forwarding path, and exit; direct connections leave more decisions to public-network routing. The cost difference ultimately reflects scheduling control, coverage breadth, and incident handling—not a simple rule that higher cost always means higher speed.

There is no need to order separate plans for different route types. 23VPN monthly subscriptions are offered by traffic tier and support Windows / macOS / iOS / Android / Linux, with unlimited devices online at the same time. Switch routes in the client and keep several candidate entry points for different tasks.

$ route.select --by task

Choose international routes by use case

Identify the target service first, then choose the region and route type. Do not start with the label that looks strongest, and do not treat one connection result as a long-term conclusion. The sequence below provides a repeatable way to choose.

> browse

Everyday browsing

For news, documents, communities, and regular websites, start with a geographically nearby entry point. Page access depends more on smooth request round trips than on reaching a distant region. If a nearby direct route is stable, keep using it; if resources load incompletely or sessions repeatedly stop, switch to a relay in the same region.

The goal of everyday browsing is to avoid unnecessary path length. Establish a baseline with a nearby route, then adjust for the region of the specific website. This is usually more sensible than always using a popular city far away.

> streaming

Streaming and content platforms

Choose an exit based on the region of the content library, then confirm that the account region, content rights, and payment region align. “Supported” in the route table means the entry point has the relevant access capability, but platforms continuously adjust regional detection rules, so the actual page shown in the client is the final test.

If video quality drops, buffering appears, or a regional notice is shown during playback, keep the account state unchanged and switch to another entry point in the same region. This separates account issues from route issues. IEPL and relay routes are generally better suited to long sessions; direct routes can be used for regional checks and as alternatives.

> ai-tools

AI Tools

AI tools often depend on web sessions, authentication, API requests, and continuous output at the same time. Prioritize a consistent exit region and avoid switching regions repeatedly within one session. If the target service mainly serves North America, start with a North American relay or IEPL route; for Asia-Pacific services, begin with a nearby region.

If the login expires, a response stops midway, or resources cannot be read, do not change several settings at once. Keep the current client configuration, replace only the route with another in the same region, and verify again. This helps identify whether the issue comes from the exit, browser state, or the service itself.

> gaming

Gaming and real-time interaction

Games depend more on continuous interaction and path changes. Prefer an entry point near the game server’s region rather than near the account registration region. If an IEPL route is available nearby, test it first; if the game server and IEPL exit are mismatched, a relay or direct route may work better.

Network acceleration cannot change the game server’s own condition or guarantee the same result on every local access network. During testing, focus on stable input response, session continuity, and whether the connection remains active after changing maps or matchmaking regions.

> work-session

Remote work and collaboration

Video meetings, cloud documents, code repositories, and enterprise dashboards are often used continuously during the same work period. Prioritize a stable exit and avoid changing regions repeatedly during a meeting or file sync. If team services are concentrated in one region, start with that region’s IEPL or relay route, and verify login and file access before work begins.

Keep a primary route and a same-region backup for office work. Use the primary for meetings and collaboration, and enable the backup only when the connection is abnormal. After switching, check that the enterprise session is still valid before resuming synchronization. For enterprise systems with fixed regional policies, follow internal access rules and do not change the exit region independently.

$ diagnose route

Choosing a route: eliminate options step by step

Assess routes like a troubleshooting command: change only one variable at a time. Changing the region, route type, client, and browser state together makes the result impossible to interpret.

target

Confirm the target region

First identify whether you are accessing a content platform, AI tool, office system, or game service, and confirm its primary service region. A content-library region is not the same as the account interface language; do not decide the exit location from page text alone.

nearby

Start with a nearby entry point

When the target service has no strict regional requirement, start with a nearby entry point. A shorter path is usually easier to troubleshoot and helps distinguish local access issues from remote service issues. Choose a specific exit directly only when the content or account policy requires that region.

fallback

Keep a same-region alternative

Keep entry points of different types in the same region whenever possible. Switch to relay if direct access is abnormal, then try IEPL if relay is unsuitable for a continuous task. Keeping the region unchanged while changing only the route type makes it easier to locate the problem.

verify

Verify the target task

Do not rely only on the client saying “Connected.” Open the service you actually need and check login, page resources, file access, continuous output, or playback. A connection status only confirms that the tunnel is established; normal operation must still be verified on the target page.

$ route check

> region matched

> service opened

> session stable

What to do first when a connection fails

First confirm that the local network can open commonly used websites, then reconnect to the current route. If the target service remains inaccessible, switch to another route type in the same region. Change regions only after every same-region entry point fails the task. This avoids aimless switching that can interfere with account region, cache, and session state.

If the browser retains information from an old region, sign out of the target service and reopen the page. For enterprise systems, payment pages, or account security checks, follow the relevant platform rules. 23VPN provides cross-border network connectivity; it does not change third-party account policies, content rights, or payment requirements.

$ coverage.inspect

How to use global coverage

The value of 110+ countries / 230+ routes is regional choice and fallback capacity—not a requirement to test every entry point. Build a shortlist for common tasks: nearby entries for everyday access, target-region entries for content and account-region needs, and same-region alternatives for troubleshooting.

The route directory may change with network conditions and service maintenance. City names indicate the exit area, while route types describe the main path organization; together they determine which tasks each route suits. Do not equate country count directly with speed or route count with guaranteed availability on a platform. Third-party detection rules, account regions, and content rights still need to be checked separately.

No email address is required to create an account; a username and password are enough. Subscriptions support Windows / macOS / iOS / Android / Linux and allow unlimited devices online at the same time. To compare traffic tiers, visit the plans page for complete billing details. All subscriptions follow the facts listed on the page and include a 30-day no-questions-asked refund.

View Plans Get the Client

Hong Kong Singapore Japan South Korea United States Canada United Kingdom Germany Netherlands Switzerland Australia Brazil