Cross-Border Network Acceleration

Global VPN Server Locations

An exit location determines where you access the internet from; a route type describes how traffic travels. Choose a region based on the service you want to reach, then compare routes using your actual apps.

Network Coverage

100+ countries 150+ routes

Below are some publicly listed exit locations. Check the client app for the routes currently available.

Location Directory

Browse Exit Locations by Region

Use this static directory to narrow down potential regions. Public information does not list the data center city, route type, or app compatibility for every location, so only confirmed exit locations are shown. To check a specific route, open the client app and review its current route list and node details.

Asia-Pacific

Country or Region
Singapore
Hong Kong
Japan

North America

Country or Region
United States

Europe

Country or Region
Germany
Italy

Other Regions

For locations not listed here, update your subscription in the client app to see the current route list. Check whether a route name refers to its entry or exit location: the exit location determines where you access the internet from.

Get the Client App

How Routes Work

International Route Types and Costs

These are common network setups, not labels for any specific exit location in the directory. The entry point is where your device first connects; the exit point is where traffic leaves the acceleration network. They describe different things.

IEPL Dedicated Line

IEPL is an international Ethernet private line, typically used to connect designated sites. A provider may use part of it for cross-border traffic, reducing that segment’s reliance on changing public internet routes. The connection from your device to the entry point, and from the exit point to the destination service, may still use the public internet. A dedicated line does not guarantee consistent performance across the entire connection.

Costs mainly come from leasing circuits between sites and provisioning capacity; upgrades usually require coordination and delivery time. For long meetings or remote desktop sessions, consider this route type and focus on recurring voice dropouts or persistent lag—not just whether a connection succeeds once.

Relay Routes

Your device first connects to an entry point, which forwards traffic to an exit point in the target region. Entry and exit locations can be arranged separately. If your local carrier’s route to a distant exit is unstable, a suitable entry point may improve the connection. However, an extra forwarding leg can also introduce a bottleneck.

Costs include entry servers, forwarded traffic, and maintenance, as well as exit resources. If you’ve already chosen an exit region, compare routes by keeping the exit fixed and changing only the entry route. Check whether browsing, uploads, and calls all improve; that tells you more than a single download test.

Direct Routes

In common usage, a direct route means your device connects straight to the remote node without a provider-operated relay in front of it. Traffic still passes through carrier networks. Skipping a relay does not guarantee a faster connection: upstream routing can take a longer path, so a nearby location may still respond slowly.

Direct routes usually avoid the cost of a separate entry relay, but still incur costs for exit bandwidth, data centers, and upstream connectivity. When the target website has no regional requirement and browsing mainly involves short requests, use a direct route as a baseline, then compare other options on the same device and local network.

Network setup costs are not the same as subscription prices and do not indicate that a plan includes a specific route type. See the plan pricing page for billing and data policies.

Use Cases

Choose a Route by App

When comparing routes, change just one factor at a time: use the same device, network, and app. Test the actions you actually perform; if you usually connect during peak hours, repeat the comparison then.

Everyday Browsing: Check That Pages Load Fully

If a website has no regional requirement, start with an exit location near your current network. Open sites you use regularly and check more than the homepage: visit an article and make sure images, search results, and links work. A fast-loading homepage with images that remain blank may indicate resources hosted on different domains, or an issue with DNS resolution or browser settings. Don’t judge a route by the homepage alone.

If only one website is affected, check whether other sites work on the same route, then try another route in the same region. If switching routes on the same device makes no difference but changing networks fixes the issue, investigate your local connection before trying more regions.

Streaming: Check Whether Video Quality Holds Up

First check what content the platform offers in your region and what quality your account and playback device support. Regional availability and a route’s ability to sustain a stream are separate issues: reaching the playback page is only the first step. Check whether the selected quality holds up during actual playback. Compare using the same title, device, and quality settings.

If playback pauses only when you seek, check whether it resumes afterward. If quality keeps dropping, pause large transfers on the same network and try again. For help distinguishing account, device, and quality limits, see the streaming guide.

AI Tools: Check That the Full Task Completes

Narrow down your options based on the service’s regional requirements, then choose an exit location that works reliably. For web tools, don’t stop at the login page: send a request and wait for the streamed response to finish. If you regularly upload attachments, include that in your comparison. Switching regions repeatedly in one session may also trigger the service’s own login checks.

For developer tools and API calls, check whether responses arrive complete and long requests stay connected. Insufficient permissions, exhausted quotas, or server-side rate limits do not mean the route is unavailable. Note the error type first, then decide whether to check account settings, app timeouts, or compare routes. See the AI tools access guide.

Gaming: Check Stability During Live Sessions

First confirm the server region used for matchmaking or your game room. Smooth downloads do not guarantee smooth live gameplay, which is more sensitive to fluctuating round-trip times and brief packet loss. Compare routes on the same game server and watch for recurring input delays, choppy voice chat, or repeated reconnections.

If voice chat and gameplay both lag at the same time, check your local network first. If only the game is affected, make sure the client’s routing rules include the actual game process, not just the launcher. Consistent performance across your usual sessions is more useful than one unusually smooth result.

Work: Check Meeting and Upload Stability

First check your organization’s requirements for access regions, devices, and networks. Video calls depend on steady uploads and downloads, while file syncing may use the upstream connection for extended periods. Test voice, screen sharing, and uploads separately, then try them together as you normally would to see whether issues occur only when tasks overlap.

Before a meeting, choose a tested exit location and a backup route. Avoid switching repeatedly during calls or sensitive sign-ins. If disconnections or inaccessible pages persist, note when they happen, your client and system versions, network conditions, and steps to reproduce the issue. Remove account and subscription details from screenshots, then follow the troubleshooting guide step by step.

Start Free