Route directory by exit region

Global server locations

Choose an exit region for your target service, then compare IEPL, relay and direct routes for your use case.

Browse routes by region

A region refers to the route's exit location. A relay's entry point and final exit may be in different regions, so choose based on the exit.

On narrow screens, swipe horizontally to view the full table. Keyboard users can focus the table and use the arrow keys.

International route examples
Country or region City Route type Streaming support
Asia-Pacific
Hong KongSee clientIEPLCheck the selected route
JapanSee clientRelayCheck the selected route
SingaporeSee clientDirectCheck the selected route
North America
United StatesSee clientRelayCheck the selected route
Europe
United KingdomSee clientDirectCheck the selected route
Other regions
No examples are listed here. Check the client for available regions, cities and route types.

This table compares exit locations and route types; it is not a complete server list. Routes in the same country or region may not work equally well with every platform, and the region name alone does not identify a content library. To check your actual exit, connect and open IP Lookup, then verify it with the target service.

Dedicated, relay and direct routes

Route types describe how traffic reaches the exit, not how fast a route is. For a fair comparison, keep your device, network connection and target service consistent.

Dedicated cross-border segment

IEPL

IEPL is an international Ethernet private line. Traffic travels from your local network to an access point, then crosses a dedicated international segment to the exit. The key difference from a regular public-internet route is that the cross-border segment is more controlled. Your device-to-access-point and exit-to-website connections remain separate network segments. A poor local Wi-Fi connection may not improve just by switching to a dedicated line.

Dedicated lines typically require leased capacity and access infrastructure at both ends, so their fixed costs are generally higher than using the public internet. Compare one during your usual hours for tasks such as video calls, remote desktop sessions or sustained uploads. Any improvement depends on whether the disruption is actually on the cross-border segment—not just on the route label.

Forwarded through an entry point

Relay

A relay route sends traffic to an entry node first, which then forwards it to an exit in the target region. This separates the entry point from the exit, allowing you to compare a different access path without changing the exit region. An entry point closer to you does not guarantee a faster end-to-end route; routing between the entry and exit also affects performance.

Relays require additional entry resources, forwarding infrastructure and transport capacity. Costs depend on the link between the entry and exit, and are not the same as dedicated-line costs. If websites load but sessions often drop, try a relay with the same exit region and see whether the task that used to stall can finish.

Direct connection to the exit

Direct

Direct means the client connects to the exit node without an extra service-side relay entry point. Traffic still passes through your access provider and public-internet routing; there is no dedicated line between your device and the exit. When the public route is smooth, direct connections avoid an extra service-side forwarding step. When it is congested, results can vary by network and time of day.

Direct routes generally avoid the cost of a relay entry point or dedicated cross-border segment, though exit and network resources still have costs. Use direct as a baseline when accessing documents, search or websites. If performance changes significantly on another access network, check your local connection and provider routing before changing the exit or trying a relay.

This compares route resource costs, not VPNI6 subscription tiers. See plan pricing for subscription fees.

Choose a route for each use case

First, identify what cannot change, such as the service's region, your gaming platform's server region or your organization's access requirements. Once those are met, compare route types. Change one variable at a time: keep the exit region the same when comparing routes, and keep the device, network and test task consistent when comparing exits. A homepage loading does not prove that the task you need will work.

Everyday browsing: compare pages you use regularly

If a site has no specific region requirement, start with an exit in a nearby region. Test with documents, search results and image-heavy pages you normally use. Check whether the text loads, images appear and browsing still works after following links. Testing a page you've already opened can be affected by caching, so a new page is more informative. If the homepage loads but images are consistently missing, first check whether related requests use the same routing rule. If several sites have the same issue, compare direct and relay routes in the same region to tell whether the problem is with one service or the access path on your current network.

Streaming: check the catalog, then test playback

Choose an exit based on the platform's supported regions and account rules. A regional homepage or correctly displayed posters do not guarantee that a particular title will play. Open the title you want to watch, start playback, seek through the video and switch subtitles to see whether the issue is catalog availability or playback. If the title is available but playback keeps buffering, try another route in the same exit region so you can compare connection paths without changing content availability. If other devices work normally, check the current device's Wi-Fi and routing mode before switching regions. Actual playback availability is determined by the platform.

AI tools: test the full response

Check the service's supported regions and account requirements, then choose a matching exit. Loading the website only confirms that the page opens; generating a response requires a sustained connection. Try a short prompt without sensitive information and check whether the response completes. If you need to upload a file, test that separately. If only an editor extension or command-line tool fails, check whether it uses the same network settings as your browser rather than assuming the whole device is affected. Follow the service's guidance for region, permissions or usage-limit messages. If responses repeatedly disconnect midstream, compare other routes in the same region. For more scenarios, see the AI acceleration guide.

Gaming: test a match on your actual server region

Choose an exit for the game server region you play on; the store region shown by the launcher may not match. Login, updates and matches may connect to different services. Try training mode or a casual match and check matchmaking, loading, control response and voice chat. Completing an update does not prove that matches will be stable: large downloads and continuous small packets have different network demands. If only voice chat or matches are affected, check the client and game's network requirements, then confirm that your routing rules cover the relevant connections. Keep the server region and access network consistent when comparing routes. If possible, pause large file syncs on your device so local congestion is not mistaken for a route issue.

Work: test your regular tasks during working hours

First, check whether your organization requires a specific access method. If other international routes are permitted, test your usual meetings, remote desktop sessions or document collaboration. For meetings, check audio in both directions and screen sharing; for remote desktop, watch for continuous input response and screen updates. Joining a meeting briefly does not guarantee smooth screen sharing, so test the actual task during your usual working hours and on your regular network. If only your outgoing video stutters during a meeting, pause local syncs and compare routes to the same exit. Once you find a working path, note the verified exit and routing mode. Avoid switching routes in the middle of a presentation or file upload.