Route Directory

Global Locations & Routes

Choose an exit region based on the service you want to access, then compare IEPL, relay, and direct routes. The region determines where you connect from; the route type describes how traffic reaches that exit.

Service Coverage

90+countries

170+routes

The table below highlights sample routes. For other locations and currently available routes, check the list in the client app.

Browse by Region

International Route Overview

“Sample city” refers to the route’s exit city, not the entry point of its cross-border segment. Suggested uses are starting points to try—not confirmation that a specific platform is supported or a guarantee of connection performance.

Sample Routes Across Asia-Pacific, North America & Europe
Country or Region Sample City Route Type Best For
Asia-Pacific
China Hong Kong IEPL Voice calls and remote collaboration
Singapore Singapore IEPL Southeast Asia business and uninterrupted work
Japan Tokyo Relay Accessing Japanese websites and testing routes for games in Asia-Pacific
North America
United States Los Angeles Direct Browsing US websites and accessing North American services
Europe
Germany Frankfurt Relay Accessing German websites and collaborating with teams in Europe
Switzerland Zurich Relay Browsing Swiss websites
Italy Milan Direct Accessing Italian websites and local content
United Kingdom London Direct Browsing UK websites and collaborating with teams in the UK

Compare Connection Paths

Route Types and Costs

Dedicated, relay, and direct routes aren’t a speed ranking. Route type describes how the cross-border segment is handled. Your experience also depends on your local connection, routing between the exit and destination server, and the time of day.

Dedicated Cross-Border Link

IEPL

IEPL stands for International Ethernet Private Line. Its key distinction is a dedicated transmission path for the cross-border segment, rather than relying entirely on public internet routing for that leg. The dedicated link applies to the transmission segment; it doesn’t mean you have an exit all to yourself, or that your entire connection from home to the website runs over a private line.

If interruptions would disrupt your work—such as speaking in a meeting, using a remote desktop, or uploading project files—try a dedicated route in a suitable exit region, then test the complete task. If your local Wi-Fi is unstable, switching routes won’t fix that part of the connection.

Cost considerations Usually, dedicated-line capacity must be leased and maintained, making cross-border transmission more expensive. This refers to the cost of building the route, not the price of an individual plan.

Connected Through a Relay

Relay Route

A relay route connects to an intermediate server first, which then forwards traffic to the destination exit. The point isn’t to shorten the path, but to change how your local network connects to the cross-border exit. Even when two routes use the same Tokyo exit, a relayed path may hold a connection more reliably if a direct connection from your location to Tokyo is unstable.

Relay routes are useful for troubleshooting by comparison. If a direct route to a particular region repeatedly stalls at your usual time, keep the exit region the same, switch to a relay, and repeat the same task. Changing just one factor makes it easier to identify the cause than changing both the region and route type.

Cost considerations Relay routes require additional infrastructure for the relay entry point and forwarding link. An extra leg may improve connectivity, but it can also add queueing; the label alone doesn’t predict the result.

Direct Connection to the Exit

Direct Route

A direct route generally means the client connects to the selected exit without an additional relay entry point provided by the service. Traffic still passes through carrier routing equipment on the public internet, so “direct” doesn’t mean a single physical hop. Nor does a geographically nearby city necessarily mean a shorter network path.

For everyday research, email, or access to websites in a specific region, there’s no need to switch if a direct route already works reliably. If pages load but connections keep dropping during sign-in, form submission, or downloads, try another route in the same region first.

Cost considerations With no additional relay infrastructure, the setup is usually simpler. Exit resources and carrier connectivity still cost money, so a direct route isn’t necessarily cheaper or faster.

Test Routes for Your Needs

Choosing a Route for Each Task

First check which regions the service supports, then compare routes using the task you actually need to do. Keep the device, network, and service the same where possible, and change one factor at a time to avoid mistaking an account issue or local network problem for a route issue.

Everyday Browsing

For research, email, and websites, start with a direct route that connects smoothly. If you don’t need a specific exit region, try a nearby one; if the website has regional requirements, filter by those first rather than choosing solely by geographic distance.

Don’t stop at checking whether the homepage loads. Open an article, view an image, or download a file you use regularly. If only a specific page on one website fails, check your account status or the page address first. If several websites have similar issues, try another route in the same region.

Streaming

Check the platform’s viewing regions and account requirements first, then choose a route in the relevant region. Loading the library homepage doesn’t guarantee that the title you want will play. Test the actual content, including playback startup, resuming after seeking, and sustained playback at your usual quality.

If playback starts but the quality keeps dropping, first rule out large file transfers on other devices at home, then try a different route type in the same region. If the platform reports a region, account, or licensing issue, switching between route types in the same region may not help. Compare the streaming support details with the streaming guide to tell library access issues apart from playback interruptions.

AI Tools

Choose an exit based on the tool’s published service regions and account requirements. Signing in successfully is only the first step: for chat tools, check that a full response comes through; for workflows with attachments, start by testing an upload and response using a small, non-sensitive file.

If sign-in works but long responses or code completions keep getting interrupted, keep the exit region the same and compare direct, relay, or dedicated routes. If the tool explicitly reports an account or service-region restriction, check the platform’s rules instead of repeatedly switching regions. Web apps and editor extensions may have different connection requirements, so test each separately. See the AI tools route guide.

Online Gaming

Choose a region based on the game server you actually join, not the region of the game store. Signing in or downloading an update doesn’t guarantee smooth gameplay. First confirm that the game allows the relevant network service, then test input response, character movement, and voice chat in practice or another non-ranked mode.

If issues only occur while other devices at home are downloading files, pause the transfers or compare with a wired connection. When testing different routes, keep the game server region and mode the same. Avoid switching routes during a live match, as changing exits may disconnect your session.

Meetings and Work

Follow your organization’s requirements for network access, exit regions, and identity verification. Once use is permitted, test meeting access, screen sharing, saving documents, or remote desktop on your usual network and during work hours. Don’t rely only on the client app showing a connected status.

For work that depends on long, uninterrupted sessions, start by testing a dedicated route that meets regional requirements, and note a backup route that you’ve verified. Choose your route before a meeting begins. If you do need to switch, save your work first and allow time to sign in again or rejoin the meeting. Test each device separately too, so a device-specific setup issue isn’t mistaken for a route failure.

Keep a record of one successful comparison. Note the time of use, exit city, route type, and the step where a failure occurred. If the problem happens again, repeat the same task first. To troubleshoot, take those details to the ticket form on the support page.

Try for Free