International routes

Global Server Locations

Choose an exit region based on the service you want to use, then compare route types. For streaming, check the content region; for games, check the game server region. For work, test meetings, files, and work apps together.

Browse locations

Cross-border Route Locations

The table below uses common data center cities to illustrate route selection. “Route type” suggests types worth comparing first; it is not a list of H6VPN deployments in those cities. “Best for” does not guarantee platform availability. Check the client for actual routes.

Example cities and route suggestions
Country or region Example city Route type Best for
Asia-Pacific
Hong Kong, ChinaHong KongRelayedEveryday browsing, web-based work
JapanTokyoIEPLExtended work sessions, voice calls
JapanOsakaDirectJapan-region games, everyday browsing
SingaporeSingaporeRelayedWeb-based work, AI tools
South KoreaSeoulDirectKorea-region games, browsing news
AustraliaSydneyRelayedAustralia-region services, team collaboration
North America
United StatesLos AngelesRelayedUS-region streaming, web browsing
United StatesSan JoseIEPLReal-time collaboration, extended sessions
United StatesSeattleDirectUS West Coast game servers, media browsing
United StatesNew YorkRelayedUS East Coast work apps, online meetings
CanadaTorontoDirectCanada-region services, everyday browsing
Europe
GermanyFrankfurtRelayedEurope-region work apps, document collaboration
United KingdomLondonIEPLUK-based work, extended meetings
NetherlandsAmsterdamDirectEurope-region news, web browsing
FranceParisRelayedFrance-region media, web-based work
SwedenStockholmDirectNordic websites, browsing news
Other regions
United Arab EmiratesDubaiRelayedMiddle East websites, business collaboration
BrazilSão PauloRelayedBrazilian websites, media browsing
South AfricaJohannesburgDirectSouth African websites, browsing news
ChileSantiagoDirectChilean websites, everyday browsing

An exit city is where your connection leaves the service network; it does not indicate where the destination website is hosted. A city may also have multiple entry points and routes. If the city you want is not listed in your client, start with an available route in the same region and compare based on your needs.

Network paths

Dedicated, relayed, and direct routes: what’s the difference?

The region tells you where your connection exits; the route type tells you how it gets there. When comparing route types, use the same exit region and test against the same service whenever possible.

Dedicated transport

IEPL

IEPL is an international Ethernet private line. For cross-border acceleration, a service can use dedicated links for part of the international journey rather than relying entirely on default public internet routes. Its main advantage is a more controlled path, making it worth testing for work where interruptions are costly, such as extended meetings, collaborative editing, or remote work that depends on maintaining a session.

Dedicated lines typically cost more to provision and maintain. However, a dedicated link does not mean each user gets exclusive bandwidth, nor does it mean every segment from your device to the target app uses a dedicated line. Local access, network interconnection, and the destination service all affect performance. To decide whether it suits regular use, look beyond how quickly a page first loads. Test a full workflow—meetings, sharing, and uploads—during your usual working hours.

If problems occur only on a company network or in a particular location, first check whether they persist when you use the same device on another everyday network. This can help distinguish local access issues from problems with the international route, without jumping to conclusions based on a route label.

Entry-point forwarding

Relayed routes

With a relayed route, your connection first reaches an entry point, which then forwards it to an exit in the destination region. The extra hop can provide an alternative when the public internet route from your local network to the destination is congested or takes a detour. A nearby entry point does not necessarily mean a shorter end-to-end path: the route from entry to exit and the connection from exit to the target service also matter.

Relayed routes require entry points and forwarding resources, so they typically cost more to operate than simpler direct routes. Actual costs also depend on entry point locations, how international links are provisioned, and capacity. If a page opens but images, documents, or video keep stalling, compare it with a relayed route in the same region. If the issue affects just one website, test other sites in that region first rather than assuming the entire route is at fault.

Direct connection

Direct routes

A direct route connects the client to an exit node using existing network routing, without an additional relay entry point arranged by the provider. This does not mean data travels in a straight line on a map; it still passes through ISP routes and network exchanges. When the path is a good fit, direct routes can work well for everyday browsing. Performance may vary if the path changes during busy hours.

Direct routes skip an extra provider-side forwarding layer, so their structure and operation are usually simpler and costs easier to manage. If you mainly browse, read documents, or occasionally use region-specific services, start by testing a direct route. If it handles your tasks reliably, there is no need to switch just because another route is labeled “dedicated.” If connection problems recur at the same time of day, repeat the same task over a relayed or dedicated route in the same region.

This section compares route structures and typical costs; it does not describe separate H6VPN pricing by route type. See the pricing page for subscription prices and data policies.

Use-case guide

Choose a route for your everyday tasks

Change one variable at a time. Keep the device, network, and target app fixed, then compare routes in the same region. If multiple regions meet the app’s requirements, compare across regions afterward. This makes it easier to identify the source of a problem.

Everyday browsing

If a website has no region requirement, start with a region that connects smoothly in your client. Open a news or document site you use regularly and visit several pages to check that text, images, and downloads all work. Testing only the home page can be misleading: cached content may load quickly while search, attachments, or long articles still fail to load fully.

If performance is poor on just one network, try another route in the same region on that network, then compare it with other networks you use regularly. If a page is only occasionally slow, noting when it happens is more useful than switching routes repeatedly. If several ordinary websites are affected at the same time, consider trying a different route type.

Streaming

First check whether the platform serves your target region and whether your account and content are eligible. Loading the home page, seeing titles, and actually playing a video are different tests. Play something you normally watch and check startup, seeking, and continued playback. Don’t judge performance from a trailer or the home page alone.

If the available catalog is wrong, double-check the exit region and the platform’s rules. If the catalog is right but playback keeps buffering, replay the same segment using another route type in the same region. Picture quality also depends on your account plan, device, player, and local connection. Keep those factors fixed to tell whether changing routes improves playback.

AI Tools

First check the tool’s supported regions and account requirements. A loaded sign-in page does not guarantee that chats, file uploads, or long responses will work properly. Test a typical workflow: open the workspace, submit a routine prompt, and wait for the complete response. If you regularly use attachments, test the upload and processing flow with a small file that contains no sensitive information.

If short prompts work but long responses repeatedly stop partway through, try another route type in the same exit region first, without changing regions and routes at the same time. For account, permission, or quota notices shown by the platform, follow its guidance. Repeatedly switching exit locations usually won’t provide useful information about these issues.

Online gaming

Check the game region for your character or friends rather than choosing solely by how close an exit is to you. The launcher, sign-in, matchmaking, and gameplay may rely on different services, so a successful sign-in does not guarantee a stable match. Start in training mode or a non-ranked match and check movement, input response, and voice chat before making it your regular route.

When comparing direct and relayed routes, keep the game region, device, and test time as consistent as possible. If lag tends to occur while other devices or apps are uploading or downloading on your local network, pause those tasks and try again. Switch routes only if the issue recurs on a particular route. Avoid changing exit locations once a match is underway, as this may interrupt your connection.

Remote work

First check which regions your work apps support and your organization’s network access requirements. Being able to read email does not mean meetings, screen sharing, and large file uploads will work smoothly. Test your actual workflow: open your usual work apps, access a shared document, then check meeting audio and file uploads. Whenever possible, test during your usual meeting hours; performance during quiet periods may not reflect how it works during the workday.

Once you find a route that works well, note an alternative in the same region so you can keep your exit location consistent if a problem occurs during work. When reporting an issue, include roughly when it happened, the route name shown in the client, and the action that failed. Hide account details in screenshots and don’t share your subscription link.

Try it free