VPN52 / Route Reference

Global servers
Locations and route selection

Choose an exit location first, then compare route types. Countries and cities determine where you appear to connect from; direct, relay and IEPL describe how the connection is routed. Consider these separately.

View Plans Connection Guides

Browse by region

Global route reference

The table lists regions, cities and route types only; it does not show speed-test results or live status. On narrow screens, scroll horizontally within the table.

When choosing a location, consider the target website’s service region, your account region and any requirements for your use case. A nearby exit can be a useful starting point, but geographic proximity does not guarantee a shorter route. Routes of different types in the same city may also use different entry points and forwarding paths. Streaming availability is marked consistently as subject to verification; location coverage does not guarantee a particular catalog or playback access.

Reference for regions and route types; check the user dashboard and client for current availability
Country / RegionCityRoute typeStreaming support
Asia Pacific
JapanTokyoIEPLVerify with actual access
Hong KongHong KongRelayVerify with actual access
SingaporeSingaporeDirectVerify with actual access
South KoreaSeoulRelayVerify with actual access
AustraliaSydneyDirectVerify with actual access
New ZealandAucklandDirectVerify with actual access
MalaysiaKuala LumpurRelayVerify with actual access
ThailandBangkokDirectVerify with actual access
North America
United StatesLos AngelesRelayVerify with actual access
United StatesSeattleDirectVerify with actual access
United StatesNew YorkRelayVerify with actual access
CanadaTorontoDirectVerify with actual access
CanadaVancouverDirectVerify with actual access
Europe
NetherlandsAmsterdamDirectVerify with actual access
SwitzerlandZurichDirectVerify with actual access
United KingdomLondonRelayVerify with actual access
GermanyFrankfurtRelayVerify with actual access
FranceParisDirectVerify with actual access
SwedenStockholmDirectVerify with actual access
FinlandHelsinkiDirectVerify with actual access
Other regions
BrazilSão PauloDirectVerify with actual access
ChileSantiagoDirectVerify with actual access
South AfricaJohannesburgDirectVerify with actual access
United Arab EmiratesDubaiRelayVerify with actual access

Streaming platforms assess access based on exit IP, account region, content licensing and their own policies. Being able to open a platform’s home page does not mean a specific title will play. After switching routes, test the content you actually want to watch.

Routes and costs

Route types explained

Route types describe how data reaches an exit; they are not a fixed ranking of service quality. The cost differences below are general technical characteristics and do not mean that these routes incur additional plan fees.

IEPL

Dedicated transport segment for persistent connections

A fit for work and streaming where consistent connectivity matters.

IEPL generally refers to an international Ethernet private line that uses dedicated transport resources to connect locations. In route services, it often describes a transport segment along the path; it does not mean that the entire connection, from your device to the destination website, uses dedicated resources. Local access, the entry connection, the exit network and the destination server all affect the experience, so an IEPL label does not guarantee the same performance in every environment.

This type of transport typically involves higher line procurement and resource maintenance costs. It may suit use cases sensitive to long sessions, sustained transfers and network fluctuations, such as video calls, remote work or continuous streaming. If the client offers the option, compare IEPL routes for these tasks. Judge the route by whether it handles your actual task reliably, not by its label alone. Check the dashboard to see which routes are included in a specific plan; a technical label does not imply that every account has access to every option.

Relay

Connect to an entry point, then forward to the exit

Worth comparing when the direct path from your network to the destination region performs poorly.

A relay route sends the connection to an entry node first, then forwards it along another path to the exit. An extra step does not necessarily mean a worse experience: if your connection to the entry node is better and the onward route is more suitable, it may be more stable than connecting directly to a distant exit. The entry node’s network conditions matter too; congestion, route changes or local access issues can all affect performance.

Relay costs involve entry, forwarding and exit resources, so the exit region alone does not determine maintenance costs. For everyday browsing, office web apps and file syncing, compare relay and direct routes in the same region. Keep the website, access network and time of use similar, then check whether pages load smoothly and sessions stay connected. A relay is not a fix for every issue, and changing routes will not resolve an outage on the destination service.

Direct

A more direct path that relies on public peering

A good starting point for browsing and access that requires a specific exit region.

Direct usually means the client connects to the corresponding remote access node without an intermediate relay. Data is carried primarily over public peering. “Direct” does not mean there are no intermediate network devices, nor does it guarantee the shortest physical route. Peering between carriers, cross-region routing and the return path from the destination network can all make the same exit perform differently across access networks.

Compared with dedicated transport or maintaining a relay entry point, direct routes typically have a simpler path structure, though actual costs still depend on the region, exit resources and peering conditions. Start by testing frequently used websites, then decide whether another route type is worth trying. If pages already load smoothly, there is no need to switch repeatedly just because a route has a different label. If performance changes noticeably in the evening, compare other paths in the same region and check your local Wi-Fi and background transfers.

Protocol and route type are separate dimensions: Trojan / VLESS / Hysteria2 describe connection methods, while direct / relay / IEPL describe route structure. For more on how they work together, read Protocol guide .

Choose by task

Choose routes for browsing, streaming and work

Start with the destination service’s regional requirements, then consider session continuity and route type. Don’t decide based only on city distance or the order shown in the client.

Everyday browsing

Start by checking whether pages load smoothly.

For research, reading documents and accessing international sites, focus on reliable page loads and intact images and login sessions. Start with a commonly used nearby region and compare direct and relay routes on the same websites. If a particular page won’t load, first check whether the issue is limited to that site rather than changing all your settings. Split tunneling should send requests that need an international route through the appropriate path, so unrelated traffic does not complicate troubleshooting.

Streaming

Test the content first, then check for uninterrupted playback.

Choose a region that matches your account and the content you want, then try playing the actual title—not just opening the platform’s home page. Signing in and playing content are separate checks. Persistent buffering may be caused by your local connection, route congestion, the exit path or the platform’s content delivery. Compare relay and IEPL routes in the same region under similar playback conditions. Changing regions does not replace a platform subscription or guarantee ongoing access to a specific catalog.

AI tools

Use a stable exit that meets the service’s regional requirements.

When accessing ChatGPT, Claude or other AI tools, first check the service’s current regional and account requirements, then choose a suitable exit. Being able to open the site does not mean your account, feature access or model requests meet all requirements. After signing in, try to keep the same region and connection method, and check that conversations, file uploads and longer responses work as expected. If you see an account notice, distinguish service requirements from connection issues before switching regions repeatedly.

Gaming

Match the game server region and check protocol compatibility.

Gaming depends on consistent input response and stable sessions; geographic proximity is only a starting point. Check the game server region, how the client works and whether the selected route is actually in use. Download performance does not predict gameplay, and website access does not confirm game protocol compatibility. The service’s route descriptions are not a promise of gaming-specific optimization. Follow the platform’s rules and test compatibility in the actual game before deciding whether to use a route.

Remote work

Keep a consistent work exit and a verified alternative route.

Work often involves video calls, collaborative documents, code repositories and file syncing. Start with your work platform’s access requirements, keep the exit region consistent and avoid switching during a session. For tasks that need longer connections, compare relay and IEPL routes for continuity and keep a tested alternative available. If your organization provides a dedicated network or device management policy, confirm which connection methods are allowed. Personal route settings cannot replace enterprise account authorization or security policies.

From selection to verification

Check your connection

Change one condition at a time. Keep the route name and details of what you were doing when the issue occurred; this is more useful than repeatedly resetting the client.

Check your local connection first

Confirm that regular websites load, pause background transfers that could affect your assessment, and check whether other network-management tools are running on the device. Weak Wi-Fi or local network congestion can make every exit seem unreliable. Check your local connection before comparing routes to avoid mistaking a local issue for a remote one.

Then check the exit and routing rules

After connecting, use IP lookup to check exit information. The result reflects only that request’s path and does not replace testing each app. If you use split tunneling, confirm that the target service is assigned to the intended group. If a page’s main request and supporting resources use different paths, the page may load while some features remain unavailable.

Compare routes in the same region

Keep the exit region the same while comparing available route types to help distinguish path issues from regional requirements. If changing the route makes no difference, consider another region based on the target platform’s rules. Don’t treat opening a home page, signing in and completing an actual task as the same result. Recording exactly where the process fails makes it easier to choose what to check next.

Still having issues? Submit a support ticket

Use the support ticket portal in the user dashboard to share your device platform, the route name shown in the client, your access network and what went wrong. You can describe an error page, interrupted playback or a failed file upload. Do not send your password or full subscription link. A clear description helps distinguish account status and client configuration issues from problems with the destination service.

Get clients and subscriptions from the user dashboard

Supports Windows / macOS / iOS / Android / Linux, with unlimited devices. Sign in to get the client on all platforms except iOS; the iOS download option is available based on your plan status shown in the dashboard. Sign in to get your subscription and keep it secure.

Get the client

For account and billing details, visit the Support Center. No email address is required; create an account with a username and password. The service keeps no logs. Route selection does not change your plan’s data limits; see the plans page for pricing and allowances.