Choose an exit region based on what you need to do, then compare IEPL, relay, and direct connections. For international routes, map distance is only part of the picture; the path an app actually takes matters too.
Local networkRelay availableExit location
International Route Coverage
These route notes are organized by exit region and are not a complete server list. For route types not specified here, check the user dashboard.
Regions, cities, and route types
Country or region
City
Route type
Streaming support
Asia-Pacific
Japan
Tokyo
IEPL
Check by platform and exit location
Hong Kong
Hong Kong
Relay
Check by platform and exit location
Singapore
Singapore
Direct
Check by platform and exit location
North America
United States
Los Angeles
Check the dashboard
Check by platform and exit location
Canada
Toronto
Check the dashboard
Check by platform and exit location
Europe
Italy
Milan
Check the dashboard
Check by platform and exit location
Other regions
For cities and routes in other countries or regions, check the user dashboard.
IEPL, Relay, and Direct Connections
IEPL describes a transmission segment; relay and direct describe the access path. When choosing a route, consider the path, exit region, and platform support separately.
Dedicated line
IEPL
IEPL is an international Ethernet private line. A route may use a dedicated line for part of its cross-border transmission, but the connection from your device to the access point and the path from the exit to the app’s server still use other networks. A dedicated-line label tells you how one segment is arranged; it doesn’t mean the entire connection will necessarily be faster.
For video calls, remote work, or large file uploads, a dropped connection can be more disruptive than a slow-loading page. For these tasks, compare a dedicated line with your usual connection by completing the same workflow during your normal working hours. Dedicated lines generally involve separate link resources and leasing costs. This describes how the route is provisioned, not an extra charge for any particular route.
Access node
Relay
With a relay, your device connects to an access point first, which then forwards traffic to the chosen exit. The access city and exit city may differ; platforms usually see the exit IP address, not the access point’s location. A relay lets you choose the access point and cross-border transmission path separately.
If a direct connection repeatedly drops on one network but works on another, keep the same exit region and compare it with a relay. This makes it easier to tell whether you need a different path or a different region. Relays involve the cost of both the access node and onward transmission, and add another point to troubleshoot. Using a relay doesn’t guarantee a better connection.
Direct connection
Direct connection
A direct connection links the client straight to the exit server, without an additional relay access point provided by the service. Your internet provider still determines which routes traffic takes along the way. A city that looks closer on a map doesn’t necessarily mean a shorter network path, and the same exit may perform differently across access networks.
For browsing, reading documents, or using everyday work apps, a direct connection is a useful baseline for your first comparison. Skipping a separate relay access point usually means one fewer access cost, though exit and transmission costs still apply. If the current route handles your tasks smoothly, there’s no need to switch based on the label alone. If you run into issues, compare a relay or dedicated line in the same region.
Choose a Route for Your Needs
Opening the homepage only confirms that a connection was established. When choosing a route, test it against the task you actually need to complete each day.
Everyday browsing: Test your usual websites first
Start with an Asia-Pacific exit. Open the websites you use regularly, then try loading images, documents, and links within the site. Text, images, and interactive features may come from different servers, so seeing the homepage doesn’t mean everything else will load properly. Testing the pages you actually use is more useful than relying on the connection icon alone.
If only one website has a problem, check the browser or site error, then try another site on the same route for comparison. If several sites won’t load, check the client and local network first, then try another route type in the same region. This helps avoid mistaking a single website outage for a problem with the entire route.
Streaming: Check the catalog, then test playback
Choose the show first, then select the region where it’s available. Once connected, reopen the app with your usual account, search for the title, and try playing it. A missing title, a region restriction message, and repeated buffering after playback starts are different issues; they shouldn’t all be blamed on the same route.
If you can’t find a title, first check regional licensing and account requirements. If it plays but keeps buffering, compare different exits in the same region. Note the exact message before switching routes, and don’t rely only on the catalog homepage recommendations to identify your region. To distinguish account region, device requirements, and playback issues, work through the streaming guide.
AI tools: Test the complete workflow
First check the tool’s requirements for your region and account, then choose an appropriate exit. With ChatGPT or Claude, loading the website isn’t enough: sign in and send a routine prompt to confirm the full response comes through. If you regularly upload files, test uploads and responses with a file that contains no sensitive information.
If the page asks for additional verification or shows an account notice, follow the platform’s instructions rather than repeatedly switching countries or signing in again. If there’s no account notice but responses often stop midway, keep the same region and compare other routes within it. See the AI tools and routes guide for more scenarios.
Gaming: Choose an exit for your game server region
A game’s region label may not match the server’s actual location. Check the in-game region setting first, then choose an exit for that region. In the practice range or a mode that won’t affect teammates, check whether controls respond consistently, the image snaps back, or voice chat cuts out. A smooth login screen doesn’t guarantee the same experience in a match.
If lag only appears during peak hours, compare the same device and game server region at the times you usually play. Don’t judge a route by comparing daytime results with nighttime ones. You can also pause local downloads or sync tasks to check whether other activity is using your home network. Avoid switching routes during a match, as it may interrupt your session.
Work: Avoid switching routes mid-task
Follow your organization’s rules for remote access and data handling. Choose an exit that meets your company account, meeting platform, or document system requirements, then test sign-in, opening a shared file, saving edits, and joining a meeting in your usual order. Confirm that voice and screen sharing work as well; don’t stop at the login page.
Note your primary and backup routes, and test the backup path on the same device before a meeting. If something goes wrong, record the step where it happened: if only a company app is affected, check your organization’s access settings first; if multiple apps disconnect, check the local network and route. Switching may interrupt a meeting or file transfer, so do it between tasks when possible.