International routes · Quantum encryption

Servers and international routes

Choose an exit location first, then compare route types. VPNHey covers 110+ countries and 170+ routes. Check the user panel for available cities and route details.

View routes in the panel View plans

Browse routes by location

The table below lists popular locations, not the full server list. A country or region indicates an exit location; it does not mean that IEPL, relay and direct routes are available in every location.

Popular locations and details to confirm
Country / Region	City	Route type	Streaming support
Asia Pacific
Hong Kong	Check the user panel	Check the user panel	Test with your target platform
Japan	Check the user panel	Check the user panel	Test with your target platform
Singapore	Check the user panel	Check the user panel	Test with your target platform
Australia	Check the user panel	Check the user panel	Test with your target platform
North America
United States	Check the user panel	Check the user panel	Test with your target platform
Europe
Check the user panel for available countries	Check the user panel	Check the user panel	Test with your target platform
Other regions
Check the user panel for available countries	Check the user panel	Check the user panel	Test with your target platform

Location doesn’t determine route details

A location mainly indicates where your connection appears to originate when accessing a destination. A city, entry point and exit point are distinct concepts; the route name alone cannot tell you the full path your traffic takes. After signing in, choose a route based on the details in the user panel. Don’t assume unspecified properties or treat every route in the same location as identically configured.

Test streaming on the platform

Being able to open a platform’s homepage doesn’t mean the content you want will play. Your account region, content licensing, how the platform identifies the exit location and app cache can all affect playback. “Test with your target platform” is not a guarantee of support. Check playback using your own account, target content and current client.

See all available routes in the user panel. If a panel name doesn’t exactly match a location listed here, follow the panel’s current listing. If you can’t find the location you need, check with support via the support ticket portal.

Dedicated routes, relay and direct connections

These labels describe how a connection is routed, not a fixed speed tier. The explanations below clarify route labels; they don’t mean every plan or location includes every type.

Dedicated transport path

IEPL dedicated line

IEPL generally refers to an international Ethernet private line. It uses dedicated transport resources for part of a cross-border route, rather than relying entirely on ordinary public internet routing for that segment. Distinguish the cross-border segment from the end-to-end connection: your local network connection to the entry point and the route from the exit to the destination still affect the overall experience.

This type of route may be worth testing for ongoing work, longer sessions or comparison during peak evening hours. After connecting, check whether your target app works as expected instead of relying on the route label alone. Congestion on home Wi-Fi, mismatched client rules or an unresponsive website won’t automatically go away just because a route is labeled dedicated.

Cost considerations: Dedicated transport resources typically cost more to build and maintain, but that cost doesn’t translate directly into the price of an individual route on this service. Check the user panel and plan details to see what’s available and how it’s priced. This page does not define a separate surcharge for dedicated routes.

Forwarded through an entry point

Relay

With a relay, your device connects to an entry point, which forwards traffic to a further exit. This separates the device-to-entry and entry-to-exit segments, allowing different combinations to suit network conditions. A relay is not the same as a dedicated line, and the label alone doesn’t reveal what resources are used for the cross-border segment.

For everyday browsing, work apps or a mix of websites, a relay can be one option to compare with other route types. A nearby entry point doesn’t necessarily mean a shorter overall route, and extra hops don’t necessarily mean a worse experience. Compare whether pages load fully, sessions stay connected and the same task performs at different times.

Cost considerations: A relay combines entry servers, forwarding resources and exit resources, usually requiring more maintenance than a simple direct connection. Resource arrangements affect costs, so “relay” doesn’t indicate a fixed price or imply unpublished performance differences between plans.

Direct connection to the exit

Direct

A direct connection generally means the client connects to the target exit without an additional relay entry point. The route structure is more direct, but the actual path still depends on carrier interconnections and network conditions. “Direct” describes the connection setup; it is not a blanket claim about speed, stability or access to every destination.

When your local network has suitable connectivity to the target exit, you can try a direct route for everyday browsing or as a comparison when troubleshooting. If another route type works with the same exit but direct doesn’t, the path from your device to the exit may be a factor. If all route types fail in just one app, also check the app’s rules and your account status.

Cost considerations: Direct connections require fewer additional relay resources, but exit bandwidth, data center and routing conditions still vary. Direct doesn’t necessarily mean cheaper, and the route type doesn’t tell you your data allowance. Plan prices and traffic rules are determined by the published plan details.

When comparing routes, keep the exit location and task the same, then switch route types. Changing both the location and type makes results harder to interpret.

Choose an exit for your needs

First choose a location that meets the target service’s requirements, then check whether you can complete your task consistently. Geographic distance is only one factor; it can’t replace testing in the app itself.

Everyday browsing

When browsing, check that text, images, sign-in components and attachments all load properly. Start with a location suitable for the site and keep routes that load your usual pages completely. Don’t stop at a fast-loading homepage: searches, sign-ins and articles may use different domains, and blank sections can point to traffic-splitting rules.

If only some sites have issues, first check whether they’re using the expected route, then compare other options in the same location. There’s no need to keep switching exits during everyday use. Saving a regular route and a backup makes changes easier to assess.

Streaming

First check which location your target content requires, then open the playback page using your own account. Once playback starts, test seeking, switching content and watching continuously. Opening a platform’s homepage alone can’t confirm whether the content is licensed or playback requests accept your current exit.

After switching locations, an app may retain an old session or cached location. Stop playback and reopen the app using its normal process; avoid switching between multiple countries while a video is playing. If content isn’t available, distinguish between location requirements, account rules and connection issues rather than attributing every playback message to the route.

Accessing AI tools

An AI tool may handle website access, account verification and generation requests through different services. Before choosing a route, review the tool’s location and account requirements; choosing a location doesn’t replace meeting those requirements. When testing, go beyond opening the page: check sign-in, submit a request and confirm you receive a complete response.

For longer sessions, keep the same exit where possible and avoid switching locations repeatedly. If you see an account or location notice, check the target platform’s guidance first. If the page loads but a request fails, note exactly where it happens and compare another route. VPNHey provides network connectivity; it does not provide account permissions for third-party tools.

Gaming

A game’s login server, match server and content download service may be in different regions. Choose an exit based on the region hosting your actual matches, and check that your client rules cover the game process. Accessing the game’s website or downloading an update doesn’t confirm that match traffic is using the expected route.

For a fair comparison, keep the game region and local network conditions the same. Check whether controls remain responsive and whether you experience rollbacks or disconnections. Network acceleration and game-specific optimization aren’t the same thing; this page doesn’t guarantee compatibility with every game or transport method. If only the game has issues, check its service status and client compatibility notes before changing routes.

Work and remote collaboration

For work, prioritize session continuity, complete file transfers and your organization’s access rules. Test video calls, document collaboration and remote desktop separately; success loading one website doesn’t confirm that every work task will function. Choose a route before starting a call or transfer, and try to keep the exit stable throughout.

If your organization requires a fixed exit, IP allowlisting or a specific network setup, confirm the requirements with your IT administrator first. A location does not guarantee a fixed IP. This service allows unlimited simultaneous devices, but each device may have different local network conditions and rules. Check devices individually rather than using the device count to judge the experience on any one device.

Verify and troubleshoot your connection

Treat “client connected” and “the task works” as separate checks. A reproducible description of the issue is more useful than simply saying “the route doesn’t work.”

Check your device and rules first

Confirm your local network can access everyday pages, then check that the subscription is updated in your client and that the selected route is listed. Review proxy mode and traffic-splitting rules to make sure the target app uses the intended route. If your browser works but an app doesn’t, check the app’s network settings before switching all your routes.

VPNHey supports Windows / macOS / iOS / Android / Linux. The user panel is the central place for the client and subscription links. Sign in to get your subscription; on platforms other than iOS, you can download the client after signing in. On iOS, access to the download link requires an active plan. No email address is required; create an account with a username and password.

View the getting started guide

Then compare routes and destinations

Compare options in the same location first, then decide whether to change locations. Change just one factor at a time and repeat the same task. If an issue occurs only in the evening, note when it happens and what type of local network you’re using. If only one site fails, record its error message and the action that failed; don’t generalize from one destination to the entire connection.

When submitting a support ticket, include the client name, device operating system, route name, approximate time and a screenshot with sensitive details obscured. Don’t share your account password or full subscription URL. For company systems or private documents, hide sensitive content first, then say whether the issue occurred during sign-in, loading or transfer.

View the troubleshooting guide