Server & Route Guide

VPN server locations
Route Types & Selection

Start with the exit region, then consider the route. The region determines how services identify your location; the route type describes how cross-border traffic is carried. Your experience will depend on your own network and should be tested there.

  • 100+ countries
  • 180+ routes
  • Unlimited simultaneous connections

No email address required. Sign up with a username and password.

Browse by region

Browse routes by region

VPNHY lists coverage of 100+ countries / 180+ routes. The examples below illustrate regions, cities and route types; they are not a complete inventory or live availability list. Check the client after signing in for currently available locations and route types.

Regional route overview; verify streaming access on the platform itself
Country / Region City Route type Streaming support
Asia-Pacific
Hong KongHong KongIEPLCheck in the client
SingaporeSingaporeRelayCheck in the client
JapanTokyoDirectCheck in the client
JapanOsakaRelayCheck in the client
South KoreaSeoulRelayCheck in the client
AustraliaSydneyDirectCheck in the client
New ZealandAucklandRelayCheck in the client
North America
United StatesLos AngelesRelayCheck in the client
United StatesSan JoseDirectCheck in the client
United StatesNew YorkRelayCheck in the client
CanadaVancouverDirectCheck in the client
CanadaTorontoRelayCheck in the client
Europe
United KingdomLondonRelayCheck in the client
GermanyFrankfurtRelayCheck in the client
FranceParisDirectCheck in the client
NetherlandsAmsterdamRelayCheck in the client
SwedenStockholmDirectCheck in the client
SwitzerlandZurichRelayCheck in the client
Other regions
BrazilSão PauloRelayCheck in the client
ChileSantiagoDirectCheck in the client
South AfricaJohannesburgRelayCheck in the client
United Arab EmiratesDubaiRelayCheck in the client

After signing in, get your subscription from the user dashboard and check current routes in the client. This reference table cannot tell you whether a route is connectable right now, and does not replace testing the connection in the client.

How routes work

Differences between dedicated routes, relay and direct connections

These terms describe connection paths, not quality tiers. Understanding how traffic reaches its exit is more useful than judging speed by the route name alone. The cost differences below describe typical infrastructure needs; they do not mean each route type has a separate fee.

IEPL

Dedicated routes: focus on the cross-border segment

IEPL usually refers to an international Ethernet private line connecting regions over a relatively defined carrier path. Compared with routes that rely entirely on public internet transit, it puts more emphasis on controlling the transport path. It can suit tasks that are sensitive to sustained connections, meeting audio or extended interaction.

Building or leasing dedicated capacity usually costs more, but the label alone does not guarantee end-to-end performance. Local access from your device to the entry point and the onward route from the exit to the destination can still affect the connection. Wireless fluctuations and busy destination services are not automatically eliminated by a dedicated route.

What to check: Test the route during your usual hours and see whether it stays connected throughout the task, rather than checking only whether a homepage loads.

RELAY

Relay routes: rerouting traffic through an entry point

With a relay route, your device connects to an entry point, which then forwards traffic to the exit. The benefit is not that every intermediate step disappears, but that the cross-network path can be arranged differently. If your local carrier's direct route to an overseas exit is poor, a suitable entry point may improve the connection.

This setup relies on the entry point, relay path and exit working together. It typically involves more resources and maintenance than a single-exit route, and costs depend on how the path is designed. An extra relay does not necessarily make a connection slower, and a relay does not guarantee greater stability. Consider the entry point, carrier peering and time of use together.

What to check: Keep the exit region the same and compare different paths on the same task, so you don't mistake a regional difference for a route-type difference.

DIRECT

Direct connections: device connects to the exit

A direct connection usually means your device connects to the target exit without an additional relay entry point set up by this service. “Direct” here means direct compared with a relay setup. The underlying internet still involves carriers and routers; it is not a physical, dedicated link between your device and the data center.

A direct setup is relatively simple and generally uses fewer relay resources, but its performance depends more on the public internet path between your local carrier and the exit. It may work well when peering is favorable, but performance can vary when networks are congested. Geographic distance alone is not a reliable way to predict the result.

What to check: Test it on the networks you regularly use. Someone else's experience with a direct route may not reflect the network your device is currently on.

Choose by use case

Choose a route for the task

Start with the task's constraints: does it require a particular region, a consistent exit, or a long-running connection? Meet those needs first, then compare day-to-day performance to avoid unnecessary switching.

Browsing

Everyday browsing: start with the sites you use most

For reading, research or messaging without a specific region requirement, start with a commonly used Asia-Pacific route. Use the same route to open the sites you visit regularly, and check that page content, images and sign-in flows work as expected. Then decide whether to keep it as your everyday option. One site loading slowly now and then does not mean the entire route is unusable.

If you can already complete your tasks, there is no need to switch just because another region ranks higher. Keeping a tested backup route is more practical. If something goes wrong, first check whether the issue affects just one site, then compare other routes in the same region.

Streaming

Video streaming: check the region, then test playback

Streaming is first and foremost about content licensing by region. Platforms such as Netflix and HBO may show different catalogs based on your exit location and account details, and titles can change as licensing agreements change. Check which region has the catalog you need, then confirm your account is eligible to play it. Catalog differences are not necessarily network issues.

When testing, check more than whether the cover image or preview loads. Make sure full playback, seeking and resuming work as expected. Picture quality depends on the content, device, account plan and network. This page does not guarantee a particular quality level or permanent access to any service. If a region notice appears, note the platform's message and your exit region before trying another route.

AI Tools

Interactive AI tools: keep your region and setup consistent

Tools such as ChatGPT, Claude and Gemini may check service region, account eligibility and exit IP reputation. A working route only addresses part of the connection; it does not replace the target service's account requirements. Before choosing a route, check the tool's official list of supported regions and use an account and network setup that complies with its rules.

After signing in, keep the region and exit consistent where possible, and avoid switching routes frequently during a session. Test sustained output, loading conversation history and any attachment features you need—not just the sign-in page. Developers should also check proxy settings in their browser, command line and IDE separately, as they may use different network paths. For a more complete checklist, see the complete guide to accessing AI tools.

Gaming

Online gaming: match the game server region and client settings

For gaming, first confirm which game server you actually connect to rather than choosing an exit based only on your account region. The launcher, game updates and live sessions may use different addresses; access to the store does not mean gameplay traffic follows the same path. Also check that your client rules cover the required game processes, so some connections do not continue over your original network.

A route name cannot prove that a connection suits a particular game, and does not guarantee competitive performance. Test during actual gameplay for sustained connectivity, repeated reconnects and working voice chat. If something goes wrong, first check for local wireless interference and background transfers, then compare other routes in the same region. Finish your current match before switching to reduce the risk of disruption.

Work

Remote collaboration: prioritize session continuity and company policies

Remote meetings, code hosting and cloud documents often require long-running sessions. Prioritize regions and paths you have tested, and check that video and audio calls, document saves and file syncs complete reliably. If your organization requires a fixed exit or an access allowlist, confirm the requirements with your administrator first; a shared subscription route should not be treated as a static IP service.

If you also use a corporate network client, check for conflicts in routing and DNS settings. VPNHY allows unlimited simultaneous connections, but device limits and the login rules of specific business systems are separate matters. Follow your organization's data-handling policies for work files. “Bank-grade encryption” is a connection-security claim, not a substitute for device permissions, account protection or internal compliance procedures.

Checks to make before and after switching

Route comparisons become unreliable when too many conditions change at once. If you change regions, devices and client settings together, even an improvement won't tell you what made the difference. Keep the device, network and task the same; change only the region or route type each time, and note the exact message shown by the destination site.

Check your local network first, then your subscription

Disconnect first and make sure your local network can access the internet normally. Then check that the current subscription is imported in the client, its status is valid and traffic is available. Monthly plan traffic resets each month on the activation date. Data add-ons remain available until used and never expire. Check the status of each billing option in the user dashboard; the subscription appearing in the client list alone does not prove it is active.

Compare routes in the same region, then consider changing regions

If the service requires a consistent region, first compare relay, direct or dedicated routes within that region. After switching, disconnect the old route and reopen the target app to test. Some apps keep existing sessions, so changing routes does not mean an existing session immediately uses the new exit. Save your work before reconnecting.

Describe the issue in reproducible steps

If the problem persists, note the platform, route name shown in the client, time of the issue and the target service's error message. Mention whether it also occurs on other routes. Do not share your password, full subscription URL or access credentials. Send these details through a support ticket in the user dashboard to make troubleshooting easier than a general report like “the connection isn't working.” For setup and importing instructions, see Guides; for common connection issues, check the Help Center.