Route directory

International routes and server locations

Choose a route based on where you need to connect and how traffic gets there. Streaming in the living room, using AI tools at your desk, and handling files on the go may each call for a different connection.

Route coverage 110+ countries / 230+ routes

Routes by region

Here are some available routes and regions to help you decide where to start. Country and region names indicate the exit location, not the city where a data center is located. Check the client after signing in for the exact route names. Suggested use cases are starting points, not compatibility guarantees for any website or app.

Asia-Pacific

Asia-Pacific routes with a listed type
Country / region Route type Best for
Hong Kong, China IEPL Try this first for extended streaming sessions
Japan Relay Compare with other routes when accessing sites in Japan
Singapore Direct A direct-route reference for everyday browsing

North America

North American exit locations
Country / region Best for
United States Test access to AI tools according to their service-region requirements

Europe

European exit locations
Country / region Best for
Italy Access sites in Italy or test cross-border connections for work

Other regions

For destinations not listed here, sign in to the dashboard to get your subscription, then browse by region in the client. If an app has no specific exit-location requirements, try a candidate region and test it with the websites or files you actually use.

Go to user dashboard

Dedicated routes, relays, and direct connections

The exit region tells you where traffic reaches the service you want to access; the route type describes how traffic gets to that exit. The same destination may be reached by different paths. Filter by region first, then narrow your options by route type.

Dedicated transport

IEPL routes

IEPL stands for International Ethernet Private Line. In network acceleration services, it usually means that one segment of the international route uses a dedicated link—not that the entire connection from your home device to the destination site is private. There is still a segment from your home to the entry point and another from the exit to the site. Congestion anywhere along the way can cause slowdowns.

These links typically involve separate procurement and maintenance costs. Their main advantage is more control over routing and capacity, not a guarantee that every page will load faster. If you often stream during evening peak hours or attend long meetings, try one during the times you normally use it. If your TV uses Wi-Fi and other devices in the same spot also have connection issues, troubleshoot your home network first, then compare routes.

Entry-point forwarding

Relay routes

A relay route connects to an entry point first, which then forwards traffic to the exit. The extra forwarding step adds operating costs but also allows more flexibility in choosing a path. If your local carrier has a poor route to the target exit, forwarding through an entry point may work better than connecting directly. A relay is not automatically a dedicated line; the transport method between the entry and exit depends on the specific route.

A smooth connection to the entry point is only the first step; both segments need to be stable. If a site often fails to load fully over a direct connection, compare it with a relay route using the same exit region. Keep your browser, Wi-Fi network, and client settings unchanged during the test so you can tell what made the difference.

Direct access

Direct routes

A direct route generally means the client connects to the exit server without an additional relay entry point. Traffic still passes through multiple routing hops on the carrier network. With no separate relay resources, the route and its operations are usually simpler; performance depends more on the path from your local carrier to the exit.

For browsing, reading documents, or looking things up, start with a direct route as your baseline. If pages load quickly and follow-up actions work smoothly, there is no need to switch just because another route has a more complex name. If things work during the day but regularly stall on the same action in the evening, try another route in the same region at the same time, then decide whether a relay or dedicated route is worth testing. Differences in route resource costs do not determine the price of an individual route.

Choose a route by use case

Check the target service's region and account requirements first, then choose a route to test. Use the same device and network, and repeat the same task for each comparison. Whether it gets your actual work done is more useful than passing a single connectivity test.

Everyday browsing: start with a direct route

Open a website you use regularly, visit a page with images, then try searching and moving between pages. A cached homepage may load even when search requests are failing. If only one site has a problem, check whether it shows a site error or a connection failure, then compare it with a similar site. If several unrelated sites stall while loading, try another route to narrow down the cause.

Streaming: test during your usual viewing hours

First make sure the title is available in the region associated with your account, then test playback on the device you actually use. Check that playback remains smooth after it starts, and try seeking to see whether it resumes properly. If a browser works but your TV keeps buffering, compare wired and Wi-Fi connections on the TV first. If picture quality only drops frequently during evening peak hours, compare routes to the same exit region. A working connection does not guarantee that a particular title will be available.

AI tools: keep the exit location consistent

Choose an exit location based on the tool's published service regions and account requirements. After signing in, send a simple request and check whether a longer response arrives in full. If the tool supports file uploads, test with a small file that contains no sensitive information. If it reports an account or region issue, check your account against the tool's guidance first. Avoid switching exit locations repeatedly in the same session; keeping the route consistent makes it easier to distinguish account restrictions from connection interruptions.

Gaming: check the server region first

Choose a route based on the region of the game server you actually connect to, not just the exit location closest to you on a map. A fast-loading store page does not guarantee smooth gameplay. Test in training or another non-ranked mode, and watch for inconsistent response times or choppy voice chat. If the game performs better with a direct connection, leave it direct and reserve acceleration routes for apps that need them.

Work: test each part of your workflow

Check your organization's access requirements to find out which tools can use international routes, especially internal systems managed by a corporate network. Smooth browsing does not guarantee stable meeting uploads. Before a meeting, test your audio and screen sharing; when syncing files, use files without sensitive information to check uploads and downloads. If voice starts breaking up as soon as you share your screen, pause any file syncing before deciding whether your work devices are competing for network capacity or the route needs to change. When switching from your home network to another network, retest essential tasks rather than relying on your previous results.

Start Free