International Route Directory

Global Server Locations

Choose an exit region based on where you need to connect, then compare route types based on how they perform. A city name indicates the exit location, but says nothing on its own about route length, service availability or connection quality.

Coverage

  • 110+ Countries
  • 220+ Routes

Regional Route Guide

The table uses common data-center cities to illustrate how exit regions, route types and use cases can be matched. It is not a list of H4VPN routes currently available in each city. Check the client after signing in for the regions and route types currently available.

Use cases in the table are suggestions for comparing routes, not guarantees of results. If an app has regional requirements, check its service availability first, then select an exit in the client. If it has no regional requirements, compare connection performance on your local network.

Asia-Pacific
Country or regionExample cityRoute typeBest for
JapanTokyoDirectEveryday browsing and setting a baseline for comparison within the same region
JapanOsakaRelayedKeeping a Japan exit and comparing performance during peak hours
Hong KongHong KongIEPLComparing call stability during frequent meetings
SingaporeSingaporeRelayedComparing uninterrupted playback for connections to Southeast Asia
South KoreaSeoulDirectChecking for gaming connection fluctuations when the target server is in South Korea
AustraliaSydneyRelayedComparing file transfer performance when accessing business sites in Oceania
North America
Country or regionExample cityRoute typeBest for
United StatesLos AngelesRelayedComparing continuous playback and seeking for connections to the US West Coast
United StatesSeattleDirectComparing page response times for business sites on the US West Coast
United StatesNew YorkIEPLComparing meeting stability when collaborating with teams on the US East Coast
CanadaVancouverRelayedComparing upload performance for business sites in western Canada
CanadaTorontoDirectBrowsing business sites and documents in eastern Canada
Europe
Country or regionExample cityRoute typeBest for
GermanyFrankfurtIEPLComparing long sessions and remote operations on routes to Europe
United KingdomLondonRelayedComparing peak-hour performance for business sites in the UK
FranceParisDirectBrowsing French news and websites
NetherlandsAmsterdamRelayedComparing file sync speeds on routes to Western Europe
SwedenStockholmDirectAccessing business sites in the Nordic region
SpainMadridRelayedComparing page and attachment load times on routes to Southern Europe
Other regions
Country or regionExample cityRoute typeBest for
BrazilSão PauloRelayedComparing project collaboration and file transfers on routes to South America
South AfricaJohannesburgDirectBrowsing business sites in Southern Africa
United Arab EmiratesDubaiRelayedComparing business pages and collaboration tools in the Gulf region

Route Types and Cost Differences

The region tells you where your traffic exits; the route type describes how it gets there. Even when two routes exit through the same city, they may take different paths to reach it.

Dedicated transmission segment

IEPL

IEPL stands for International Ethernet Private Line. With this type of route, a provider can use a dedicated transmission segment between the access point and the exit, and plan its capacity and routing. Leasing, maintaining and expanding this infrastructure costs money, so these routes generally cost more than options that rely solely on the public internet. This refers to the cost of building the route, not an extra fee for a particular plan.

If cross-border meetings or remote operations often stutter briefly at set times, an IEPL route is worth comparing. It can improve control over the transmission segment it covers, but it does not turn your local Wi-Fi, ISP connection or the route from the exit to the target app into a dedicated connection. Compare how long meetings stay stable and whether remote sessions need to reconnect, not just the initial response time.

Forwarded through an access node

Relayed route

With a relayed route, your device connects to an access node first, which then forwards traffic to the exit. The access node may use a different interconnection path to avoid a poor route between your local network and the destination region, but it also adds another point where capacity, congestion and maintenance can affect performance. Costs depend on the entry, exit and transmission resources between them—not simply on the number of nodes along the way.

If a direct route performs poorly only at certain times, or your experience changes noticeably with a different local ISP, compare it with a relayed route in the same region. This helps you tell whether the improvement comes from the transmission path or simply from changing the exit region. If the same app performs poorly on both routes, look at your local network or the target service rather than repeatedly switching regions.

Connect directly to the exit

Direct route

A direct route connects your device to the exit over the existing network, without an additional provider-configured access relay. This does not mean the connection reaches its destination in a single physical hop; ISP-to-ISP routing still applies. Without a dedicated transmission segment or extra access resources, this type of route generally costs less to build. When your local network has good connectivity to the destination region, a direct route may be all you need.

For everyday browsing, research and other tasks with a short connection path, use a direct route as a baseline. If it works well during the day but frequently stalls in the evening, test the same page during the hours you normally use it. If it is unstable only on your home Wi-Fi, try a wired connection or another network first. A geographically closer direct exit is not necessarily a better choice than a relayed route with a smoother path.

Choose a Route for Your Use Case

Compare routes based on what you actually need to do, not their names. Keep the device, network and target app consistent, changing just one factor at a time to make it easier to identify where an issue occurs.

Everyday Browsing

If you have no regional requirements, start with an exit that has good connectivity from your local network. Check familiar news, search and document pages. A slow-loading page may be waiting for its main content, or just for images or scripts; the former is useful for comparing routes, while the latter may affect only certain resources. Test a page you have not opened before so your browser cache does not hide the wait. If several types of sites slow down only during your usual hours, keep the region the same and compare another route type. That makes the results easier to interpret than switching straight to another continent.

Streaming and Live Video

First check the platform's regional policies, account status and content availability. Being able to open the homepage does not mean a title will play, and being able to play it does not guarantee consistent picture quality. When comparing routes, use content you actually watch and check startup time, recovery after seeking and sustained playback—especially during your usual viewing hours. If only a particular title is unavailable, check its regional licensing and your account entitlements first. If the same title stops buffering repeatedly after you switch routes, consider setting the new route as your default. Live streams are more sensitive to brief interruptions, so startup speed for on-demand video alone is not enough to choose a route.

AI Tools

Check the platform's supported regions, account requirements and usage conditions first, then compare exits that meet them. In addition to opening the chat page, test with non-sensitive content to see whether generation continues, attachments upload and sessions stay connected. If a response stops partway through, the cause could be connection fluctuations, a busy platform or an expired session. Avoid changing exits frequently while signed in and working on a task. If you see a region, access or quota notice, check the platform's rules and your account status rather than treating it as a route issue.

Online Gaming

Choose a route based on the region of the game server you actually play on, not the region of the game's store or login page. In a practice or casual mode, compare input responsiveness, voice chat stability and connection consistency over several matches. If performance fluctuates only when someone at home is downloading files or syncing photos, pause background uploads and try a wired connection before switching routes. Decide based on performance during your usual gaming hours, even if both routes seem fine at other times. Prefer the route with fewer fluctuations, and don't switch mid-match.

Remote Work

For meetings, check whether audio and video stay consistent in both directions. For file collaboration, watch for repeated upload retries; for remote desktops, check whether small actions get a timely response. Since each task has different needs, compare video and audio, screen sharing and file sync using the same exit region, then choose a primary route for your most common task. For corporate resources, follow your organization's approved remote access methods and login-region requirements. When preparing a backup, compare routes within the same service region if possible. Confirm the connection before a meeting to avoid reconnects or extra login checks caused by switching exits mid-call.

Start Free