Countries and cities describe the exit location; IEPL dedicated lines, relays and direct connections describe the connection path. These are separate factors. Routes listed for the same region may use different entry points and transmission methods.
The table below illustrates how to read region, city and route type information. It is not a complete server list, and the listed city and route type combinations may not all be currently available. Check the user dashboard and client subscription list for available exit regions, cities and route types. If a city cannot be confirmed, rely on the information shown in the client rather than inferring a data center location from a route name.
Asia-Pacific
For everyday browsing, start by comparing Asia-Pacific exits with suitable connection paths. A shorter geographic distance does not necessarily mean a smoother connection. Peering with local providers, congestion at the entry point and the destination website’s hosting location can all affect performance.
Asia-Pacific region and network path examples, not an availability list
Country/region
City
Route type
Streaming support
Hong Kong, China
Hong Kong
IEPL dedicated line
Not verified; test with your target platform
Japan
Tokyo
Relay
Not verified; test with your target platform
Singapore
Singapore
Direct
Not verified; test with your target platform
South Korea
Seoul
Relay
Not verified; test with your target platform
Australia
Sydney
Direct
Not verified; test with your target platform
New Zealand
Auckland
Relay
Not verified; test with your target platform
North America
When you need content or business access in North America, choose an exit in the relevant region. Don’t pick a route based on how well-known its city is. Application servers and content delivery networks may be located somewhere other than the region associated with a service’s brand.
North American region and network path examples, not an availability list
Country/region
City
Route type
Streaming support
United States
Los Angeles
Relay
Not verified; test with your target platform
United States
New York
Direct
Not verified; test with your target platform
Canada
Toronto
Relay
Not verified; test with your target platform
Mexico
Mexico City
Direct
Not verified; test with your target platform
Europe
Choose European exits based on the region relevant to your needs. If account region or workplace access rules apply, first confirm which regions the platform allows. A network exit changes the connection path, not your account’s region settings or eligibility.
European region and network path examples, not an availability list
Country/region
City
Route type
Streaming support
Netherlands
Amsterdam
Relay
Not verified; test with your target platform
France
Paris
Relay
Not verified; test with your target platform
Germany
Frankfurt
Direct
Not verified; test with your target platform
United Kingdom
London
Relay
Not verified; test with your target platform
Switzerland
Zurich
Direct
Not verified; test with your target platform
Sweden
Stockholm
Relay
Not verified; test with your target platform
Other regions
For region-specific content checks, business access and website testing, start with the target service’s regional requirements. Long-distance exits generally involve longer transmission paths, so they may not be the best default for every application.
Other regions and network path examples, not an availability list
Country/region
City
Route type
Streaming support
Brazil
São Paulo
Relay
Not verified; test with your target platform
Chile
Santiago
Direct
Not verified; test with your target platform
South Africa
Johannesburg
Relay
Not verified; test with your target platform
United Arab Emirates
Dubai
Direct
Not verified; test with your target platform
These are static examples for route selection only. The available exits may change with your subscription. After updating your subscription, check that your saved routes are still available.
TOPOLOGY
IEPL dedicated lines, relays and direct connections
Route type describes the path data takes, not a speed tier. A protocol describes how the client and server exchange data; it is not an exit region. Check region, network path and client compatibility separately when choosing a route. Don’t treat a protocol name alone as a performance guarantee.
1
IEPL dedicated line
IEPL generally refers to a dedicated Ethernet line. This type of connection uses a dedicated transport segment for part of the route, reducing reliance on ordinary public internet peering. The full connection still involves your local access network, the service entry point and the route from the exit to the destination website. So a dedicated-line label does not mean the entire connection stays on a private network.
A good fit for work, meetings and sustained transfers where session continuity matters. Dedicated transport resources generally cost more to build and maintain, but that is a characteristic of the network path—not a promise that VPN54 charges extra for a particular route. Stability during evening hours still depends on your local network and actual use.
What to check: Whether the connection drops during extended use, and whether reconnecting restores your workflow.
2
Relay
A relay route sends your connection to an entry point first, then onward to the exit. The entry and exit can serve different purposes: access and regional connectivity. An extra hop does not necessarily make the experience worse. If the entry point has better peering, a relay may perform better than a route without one, though congestion at the entry or forwarding stage can also have an impact.
Suitable for everyday browsing, streaming and comparing different entry points. Costs can involve entry resources, exit resources and forwarded traffic, so a relay cannot be assumed to belong to a fixed price tier. If exits in the same region perform differently, consider the entry point as well as the destination.
What to check: Compare page loads, video seeking and long-lived connections during your usual hours, then keep the route that works best.
3
Direct
Direct usually means the client connects to the selected service entry point without an additional service-side relay. The path is simpler, but still goes through provider networks and international peering. It does not mean there is only one physical link between your device and the destination website, or that performance will be the same in every region.
Suitable when your local network has good connectivity to the destination entry point and you want to simplify troubleshooting. Compared with a route using additional relay resources, direct connections have fewer forwarding steps, but actual costs still depend on the exit region and network resources. Test mobile and home broadband separately; results on one type of connection may not apply to another.
What to check: Retest after switching local networks to see whether the change comes from your access connection or the selected exit.
For a closer look at the trade-offs between Shadowsocks, VMess, Trojan, VLESS, Hysteria2 and TUIC, see Protocol and route technical guide ›. Protocol names alone don’t indicate exit quality.
SELECTION BY TASK
Choose a cross-border route by use case
Choose a route based on what you need to do, not its position in a list. First, check whether a specific region is required, then consider whether your task depends most on responsiveness, sustained transfers or session stability. Compare routes on the same device, app and similar network conditions for more consistent results.
BROWSING
Everyday browsing: compare load times and interaction
Web browsing involves DNS lookups, connection setup, page resource loading and requests triggered by your actions. A homepage loading successfully doesn’t guarantee that sign-in, uploads or search will work. Start with a route in a region you use regularly, then check the sites you visit most. If only one page has issues, check your routing rules and the destination service status before changing your entire exit region. Save a route that works well to avoid unnecessary switching.
STREAMING
Streaming: check the catalog, then test playback
Streaming requires both access to the right regional catalog and a connection that can sustain playback. First check whether the title is in the catalog, then test playback, seeking and switching video quality. Loading the platform homepage does not confirm full compatibility. The platform may consider your account region, billing region and recognized exit IP; not every content notice is caused by the route. See Streaming guide › for detailed testing steps.
AI TOOLS
AI tools: check regional eligibility and persistent connections
Check which regions the tool supports and make sure your account is eligible. A network route provides connectivity; it does not grant platform account permissions. To test, go beyond loading the page: sign in, send a request and receive a complete response. If you work with files, test uploads too. If streaming output stops while the page remains accessible, the cause may involve persistent connections, client sleep settings or routing rules. Keep the exit region consistent during a session to avoid adding variables when troubleshooting.
GAMING
Gaming: match the game region and check traffic support
Check the game server region, client proxy mode and required traffic support first. A website working normally does not mean the game process is using the same route; some apps require additional system-level network routing settings. Choose an exit that matches the game region, then check the connection in an actual match or using the game’s built-in network test. VPN54 is a cross-border connectivity subscription service. This page does not equate general international routes with dedicated gaming routes or promise compatibility with every game.
WORKSPACE
Work: prioritize continuity and access rules
Work may involve meetings, document collaboration, file transfers and access to internal systems. Follow your organization’s network and data policies, then check whether its systems restrict exit regions or IP addresses. After joining a meeting, test screen sharing, audio continuity and reconnection. If a system requires an allowlisted source IP, don’t assume a standard subscription route provides a fixed or dedicated address. Check the actual service details for available options.
VERIFICATION
From subscription list to connection test
This page offers static route selection examples; start with an active subscription to connect. No email address is required—create an account with a username and password. Sign in to the dashboard to get the client and subscription details. For Windows, macOS, Android and Linux, sign in to download a client; an active plan is required to access the iOS download. Don’t post your subscription link in public forums or share it with unfamiliar diagnostic sites—it contains your account access credentials.
1
Update your subscription list
Use the subscription update feature in your client and confirm that the current list has loaded. If the update fails, first check the subscription status in the dashboard and your local network. Don’t assume an exit has been removed based on an outdated list.
SUBSCRIPTION
Sign in to the dashboard to get your subscription
Return to the client and update the list
2
Choose a region and route
Choose an exit based on the target service’s regional requirements, then check the route type. Keep proxy mode and routing rules consistent during testing. Change only what’s necessary each time so you can tell which change affects the result.
ROUTE SELECTION
Check the exit region
Check client routing rules
3
Test with your actual use case
Open the target app and complete your usual tasks. To check your exit, use the site’s IP lookup tool. If the lookup result differs from what the app shows, check routing rules, existing connections and the app cache.