Browse Routes by Region
This table shows static examples. Cities indicate exit locations; the routes available in the client may differ from those shown here. “Not specified” in the streaming column does not indicate whether a platform is available.
| Country / Region | City | Route Type | Streaming Support |
|---|---|---|---|
| Asia-Pacific | |||
| Hong Kong, China | Hong Kong | IEPL | Not specified |
| Japan | Tokyo | Relay | Not specified |
| Singapore | Singapore | Direct | Not specified |
| North America | |||
| United States | Los Angeles | Relay | Not specified |
| Europe | |||
| Italy | Milan | IEPL | Not specified |
| Other | |||
| For routes not listed here, sign in to the user dashboard to get your subscription, then view available routes in the client. | |||
The exit city is not a list of cities the traffic passes through. Routes in the same region may follow different paths. When comparing routes, check the exit location first, then the route type.
IEPL, Relayed, and Direct Routes
Route type describes how traffic reaches the exit, not how fast a route is. Cost differences below refer to route infrastructure and operating costs, not separate prices for each type.
IEPL: Dedicated transport for part of the cross-border route
IEPL stands for International Ethernet Private Line, connecting network access points in different regions over Ethernet. In network acceleration services, dedicated transport typically covers only part of the cross-border route. It does not mean the entire path from your device to the destination website uses a private line, or that each user gets an entire route exclusively. Device access and the segment from the exit to the destination service also affect performance. For example, an unstable local Wi-Fi connection can still interrupt a call, even after switching to a dedicated route.
Dedicated transport resources usually require separate procurement and maintenance, so they generally cost more than relying directly on the public internet. For tasks sensitive to cross-border route fluctuations, such as ongoing file uploads or long video calls, consider a dedicated route alongside relayed or direct options in the same region. Testing whether it handles your actual task is more useful than judging by the route label alone.
Relay: Connect through an access point before reaching the exit
With a relay, traffic first goes to an access point, which then forwards it to the destination exit. The access point and exit can be in different regions; the city shown in the table is the exit location. A relay changes the cross-border path: if your local network has a better route to the relay entry point, the experience may be better than connecting directly to the exit. On the other hand, congestion on the access or forwarding segment—or the extra forwarding hop itself—may make performance worse than a direct connection.
Relay costs come from access resources, forwarding equipment, and transport between the access point and exit. You can’t judge them by the number of forwarding hops alone, or assume a relay is always cheaper than a direct route or more expensive than a dedicated line. If a service often stalls partway through loading over a direct connection, keep the same destination region and try a relay. That way, you’re comparing route changes rather than changing both the region and route.
Direct: No additional relay entry point operated by the service
A direct route connects the client to the exit over the public internet without first passing traffic through a separate relay access point operated by the service. Public internet traffic still follows carrier routes, so direct does not mean the shortest physical path or that data passes through only one device. When the connection between your local network and the exit is good, a direct route may be sufficient for reading websites, researching, or syncing documents. Public routing can change, so the same direct route may perform differently at different times.
Because no separate relay entry point needs to be configured for this route, direct connections usually avoid one forwarding resource cost. Use a direct route as your baseline: try a common task on your usual network and at your usual time. Only test other route types in the same region if you encounter repeated interruptions or long waits. If the direct route handles your tasks reliably, there’s no need to switch frequently just because another route has a different label.
Choose a Cross-Border Route by Use Case
Start with the region required by your target service. Once you’ve identified candidate exits, compare routes using tasks you normally do, changing one factor at a time where possible.
Everyday Browsing: Check Full Page Loads, Not Just the Homepage
For reading documents, researching, or viewing images, start with a region that’s easy to reach from your local network. Open pages you normally use and check that text, images, and pagination all load properly. A homepage loading doesn’t guarantee that its embedded resources will load too. Conversely, one page failing to open isn’t enough to conclude that the entire route is at fault. Check another familiar site before comparing other routes in the same region.
Streaming: Check Region Rules, Then Test Continuous Playback
Content libraries, account benefits, and available video quality may depend on platform rules, licensing regions, and playback devices. Before choosing a route, check which region and content apply to your account; a route’s location label doesn’t guarantee access to a particular library. During playback, check for frequent buffering after the video starts, whether playback resumes after seeking, and whether quality keeps dropping. If only one title won’t play, check the platform’s message first. If several titles have similar interruptions, compare routes in the same region using the same device and video quality.
AI Tools: Distinguish Account, Service Region, and Connection Issues
Check the tool’s officially supported regions and account requirements first. Opening the website is only an initial connection check; also see whether a normal conversation continues to return responses and whether files upload completely. As long as you comply with the service’s rules, try to keep the same exit throughout a work session to avoid interrupting tasks when switching routes. If you use an API, access through the website doesn’t mean your command line or editor uses the same network settings. Check the runtime environment first, then use the service’s response to distinguish connection interruptions from permission or usage-limit issues. Switching routes repeatedly won’t resolve the latter two.
Gaming: Go by Your Actual Match Region and In-Game Experience
Your account region, store region, and the server assigned by a game aren’t always the same. Check your usual server or matchmaking region first, then choose a candidate exit near it. Use training mode or an unranked match to check for inconsistent response times, choppy voice chat, or frequent reconnections. A closer exit doesn’t necessarily have a better route. If you need to switch, wait until the current match ends so a disconnect during the switch isn’t mistaken for an unstable route.
Work: Test Meetings and File Transfers Separately
For collaborative documents, check whether edits sync promptly. Video calls also depend on continuous audio and video, while file delivery requires a completed upload and a successful download by the recipient. We recommend testing with a sample file that contains no sensitive information on your usual network and at your usual meeting time, and noting a backup route in the same region in advance. When accessing internal company resources, follow your organization’s access policies. Use an organization-approved connection for services that require one.