International Routes

Global Server Locations

110+ countries / 190+ routes

Start with a destination, then compare direct, relay, and dedicated routes. Cities are just a starting point—choose based on the sites and apps you actually use.

Browse routes by region

The table lists common data center cities to help narrow your options. The route type column shows which paths to compare first, while the use case column suggests what to test. Neither confirms that a route is available in that city or that an app will work. Check the subscription list in the client after signing in for the cities and route types currently available.

When choosing a region, consider proximity to your device and proximity to the service separately. The first affects the connection from your device to the route entry point; the second affects the path from the exit to the destination service. If a site requires a specific region, start there. Otherwise, begin with an exit that is easy to retest on your usual network. There’s no need to rank cities by straight-line distance on a map.

Asia-Pacific

Asia-Pacific: Key Cities and Route Guide
Country or regionRepresentative cityRoute typeSuggested use
Hong Kong, ChinaHong KongDirectEveryday web browsing
JapanTokyoRelayWatching content from Japan
JapanOsakaDirectConnecting to Japan-region game servers
SingaporeSingaporeDedicated IEPLRemote meetings and screen sharing
South KoreaSeoulDirectConnecting to South Korea-region game servers
AustraliaSydneyRelayCollaboration with teams in Australia

North America

North America: Key Cities and Route Guide
Country or regionRepresentative cityRoute typeSuggested use
United StatesLos AngelesRelayWatching content from the United States
United StatesSeattleDirectConnecting to game servers in the western United States
United StatesNew YorkDedicated IEPLRemote meetings and screen sharing
CanadaTorontoRelayAccessing content from Canada
CanadaVancouverDirectWeb browsing and online documents

Europe

Europe: Key Cities and Route Guide
Country or regionRepresentative cityRoute typeSuggested use
GermanyFrankfurtDedicated IEPLRemote collaboration with teams in Europe
SwitzerlandZurichRelayAccessing services in Switzerland
United KingdomLondonRelayWatching content from the UK
NetherlandsAmsterdamDirectBrowsing European websites
FranceParisDirectAccessing content from France

Other regions

Other Regions: Key Cities and Route Guide
Country or regionRepresentative cityRoute typeSuggested use
United Arab EmiratesDubaiRelayCollaboration with teams in the Middle East
South AfricaJohannesburgRelayAccessing websites in South Africa
BrazilSão PauloRelayCollaboration with teams in Brazil
ChileSantiagoDirectBrowsing websites in Chile

Dedicated IEPL, Relay, and Direct Routes

Route names describe how traffic travels from your device to the exit, not a fixed ranking from fastest to slowest. When evaluating a route, consider each leg: device to entry point, entry to exit, and exit to the destination website. If switching routes doesn’t solve the problem, the change may have affected the transport path while the issue lies with your local network or the destination service.

Dedicated Ethernet transport

Dedicated IEPL

IEPL usually refers to an International Ethernet Private Line. In network acceleration services, a dedicated circuit generally carries traffic between specified endpoints; the connection from your device to the entry point and from the exit to the application server may still use public networks. “Dedicated” describes one leg of the route. It doesn’t mean each user gets an entire link to themselves or that bandwidth is consistent end to end.

Leasing circuits, deploying access at both ends, and maintaining capacity typically add cost. Consider a dedicated route for frequent meetings, extended screen sharing, or regular file uploads. When testing, check for choppy speech, frozen shared screens, and successful uploads rather than judging by a single page load.

Routed through an entry point

Relay

A relay sends traffic to an entry point first, then forwards it to an exit in the destination region. With a suitable connection from your device to the entry point, a relay may avoid some poor public-network routes. But an unstable connection to the entry point, a detour through the relay, or limited capacity can offset that benefit. The exit region can differ from the entry point’s region, so don’t choose based on the entry point name alone.

Compared with a direct route, a relay requires additional forwarding nodes and connections to maintain, with costs depending on entry point deployment and transport resources. If direct connections vary noticeably by time of day, compare direct and relay routes in the same region on the same device and network. If an issue occurs only on your work network, you can also retest on another permitted network to distinguish access conditions from route differences.

Direct connection to the exit

Direct

A direct route connects the client to the selected exit without an additional service-side relay entry point. It still passes through carrier backbones and network exchange points, so it doesn’t necessarily follow the shortest physical path. Even when using the same exit, home, office, and hotel networks may route traffic differently and deliver different results.

A direct route avoids an additional relay segment and usually the related operating costs. Use it as a baseline for everyday browsing, email, and documents. If pages load normally and files upload successfully, there’s no need to switch from a route that works just because of its name. If one site keeps failing, check its service status before comparing other paths.

Choose a route for what you do

Test routes with the tasks you actually perform. Change only one variable per round—region or route type—and repeat tests under similar network conditions and at similar times. This makes it easier to identify what improved and keep a reliable backup route.

Everyday browsing: test websites and attachments

If you don’t need a specific region, start with an exit that’s easy to connect to. Open a familiar news page, email, or online document, then wait for images and attachments to finish loading instead of checking only whether the homepage opens. If the headline appears quickly but the rest takes a long time to load, retry in the same browser and compare with a relay in the same region. If the issue occurs in only one browser, check its extensions or cache first.

Streaming: distinguish catalog, errors, and buffering

First check the platform’s service regions, account region, and content licensing. Test only where the platform’s terms allow. Troubleshoot titles that aren’t available separately from titles that appear but won’t play: check the catalog in the first case and the app’s error message in the second. Once playback starts, test seeking and continuous playback. If quality starts out clear but drops repeatedly, compare another route in the same region and check whether other devices on the network are using substantial bandwidth. See the streaming guide for more details.

AI tools: test the full workflow

Start by checking the platform’s published service regions and account requirements. In line with the platform’s rules, test signing in, sending a request, waiting for the full response, and uploading files if needed. A page loading doesn’t guarantee that a longer response will finish successfully. If you see a permissions or usage notice, check your account settings first; if a transfer is interrupted, retry the same request on another route. Use non-sensitive materials when testing uploads.

Gaming: test the actual game server

First check the game region and client connection requirements, then compare exits close to the actual game server. A fast launcher download doesn’t guarantee responsive gameplay, since downloads and matches often use different servers. Test controls and voice chat in a practice area or non-ranked mode. If you see players teleporting or hear choppy voice chat, pause background syncing and compare direct and relay routes. Keep your current connection if there’s no consistent improvement.

Work: test uploads and screen sharing

Connect to meeting and collaboration systems in accordance with your organization’s network policies. During testing, don’t just listen—try speaking, sharing your screen, and uploading a document, then ask a colleague whether the audio and video are smooth. A connection that works at the office may not work the same way elsewhere. On hotel or shared networks, make sure network access is fully set up before testing routes. Test a backup route before important meetings; don’t keep switching during a meeting just to compare performance.

When performance fluctuates: narrow down the issue

First check whether regular websites and the target app are both affected. If everything is unstable, check your local network before switching routes. If only one app has a problem, check its service status, account, and region requirements first. When contacting support, share your device platform, the time it happened, route name, and exact error. Remember to hide account details and subscription URLs in screenshots. If you need to set up the client again, follow the client setup guide to check the import and connection steps.

Start Free