International Route Index

Global Server Locations

Start with the region where your service operates, then compare direct, relayed, and IEPL routes. Test with the sites or apps you actually use rather than choosing by city name alone.

The table lists representative cities and route types to compare in each region. It is a selection guide, not a list of live server locations. Suggested use cases are for testing and do not guarantee platform availability. Sign in to the user dashboard to see currently available routes.

Asia Pacific Routes

When accessing services in Asia Pacific, start with the region where the service operates. If multiple cities are available in the same country, keep your use case constant and compare route types.

CountriesRepresentative CityRoute TypeUse Case
ChinaHong KongIEPLMeetings, continuous data transfer
JapanTokyoRelayedJapanese websites, online collaboration
JapanOsakaDirectCompare direct routes in the same region
SingaporeSingaporeDirectAsia Pacific websites, everyday browsing
South KoreaSeoulRelayedKorean services, game connectivity testing
AustraliaSydneyDirectAustralian websites, regional service testing

North America Routes

US and Canadian exits serve different regional needs. If your use case doesn't specify a city, try the East or West Coast based on where the target service operates, then compare using the same task.

CountriesRepresentative CityRoute TypeUse Case
United StatesLos AngelesRelayedUS West Coast services, streaming response tests
United StatesSeattleDirectUS West Coast services, direct-route comparison
United StatesNew YorkRelayedUS East Coast services, remote collaboration
CanadaVancouverDirectBrowsing Canadian West Coast websites
CanadaTorontoRelayedCanadian East Coast services, file collaboration

Europe Routes

When accessing European websites, first check which country the service recognizes. Sites serving different markets may not be interchangeable, even when they are geographically close.

CountriesRepresentative CityRoute TypeUse Case
GermanyFrankfurtRelayedGerman services, remote work
United KingdomLondonDirectUK websites, regional content checks
NetherlandsAmsterdamDirectDutch websites, everyday page loading
ItalyMilanRelayedItalian services, business dashboard testing
FranceParisDirectFrench websites, site version checks

Routes in Other Regions

For regional services in the Middle East, South America, and Africa, first check the target country, then confirm that sign-in, form submissions, and file transfers all work as expected.

CountriesRepresentative CityRoute TypeUse Case
United Arab EmiratesDubaiRelayedAccessing services in the Gulf region
TurkeyIstanbulDirectTurkish websites, localization checks
BrazilSão PauloRelayedBrazilian websites, cross-region form testing
South AfricaJohannesburgDirectSouth African websites, regional service testing

Connection Methods

Route Types and Cost Differences

The region tells you where traffic exits; the route type tells you how it gets there. You don't need to change countries to compare route types: keep the exit region the same and test with the same task to see how the paths differ.

IEPL

IEPL stands for International Ethernet Private Line. For users, the key point is that the cross-border backbone segment uses a private line rather than relying entirely on public internet routing. Traffic still travels over your local network before reaching the private line and must connect to the target service after leaving it. So a private line doesn't replace checking your local Wi-Fi, exit point, or target service.

Private lines require cross-border circuits to be provisioned and maintained, so their resource costs are generally higher than routes that rely only on the public internet. They're worth comparing first for long meetings, continuous uploads, or remote desktop use. Check for repeated audio dropouts, laggy controls, and uploads that fail to complete. If your local connection is unstable, switch networks and test again before attributing the problem to the cross-border segment.

Relayed Routes

A relayed route first connects to an access point, which then forwards traffic to an exit in the target region. The access point and exit don't have to be in the same region. The extra hop lets you choose a different path from your local network to the exit. If the relay's data center has better connectivity with your local carrier, the experience may be better than connecting directly to the exit, even with the additional forwarding leg.

Relayed routes require additional access and forwarding resources, and depend on the links between each segment. If a direct route repeatedly fails to load images or interrupts streaming responses during your usual hours, keep the target region the same and test a relayed route. Keep the connection active until the task is complete; a successful handshake alone doesn't show whether uploads or ongoing requests will be reliable.

Direct Routes

With a direct route, the client connects to the exit server without an additional service-side relay access point. Network operators still forward traffic hop by hop over the public internet, so a direct route isn't a straight geographical path, and different access networks may take different routes. Results on a home network may not apply to an office network.

Direct routes avoid private-line circuits and extra forwarding hops, making their resource setup relatively simple. For everyday browsing, document access, or short sessions, start with a direct route as a baseline. If everything works smoothly, there's no need to switch just because another route sounds more advanced. This compares route resource costs, not per-route prices for users. See the plans page for subscription pricing.

How to Test

Choose a Route by Use Case

Use the same device and network, and compare routes during your usual hours. Change only one variable at a time—region or route type—and note where the task fails. This makes it easier to pinpoint the cause than changing the route, client, and network all at once.

Everyday Browsing

If you don't need a specific region, start with a nearby direct exit. Visit a site you use regularly, open its homepage, then view a detail page, load images, and submit a search. A homepage may load from a local cache, so don't judge by the first impression alone. Visit the same content before and after switching, and note whether the issue affects just one site.

If the page layout loads but images and scripts don't, check whether other sites are affected too. If it's only one site, check whether the site is under maintenance or its resource domains are reachable. If several sites are slow at the same time, compare with a relayed route in the same region. The main measure is whether you can browse without interruptions.

Streaming

Check the streaming platform's published regional, account, and device requirements first, then choose an exit in an eligible region. Loading the homepage doesn't guarantee the same library, subtitles, or playback access on your account. A route name can't confirm that a specific title will play. If the platform says your region or account isn't eligible, check its rules first.

Test with something you usually watch. Check playback start, continued playback, and recovery after seeking. Seeing a cover image or a smooth opening isn't enough to judge the full experience. If buffering occurs, keep the quality and network constant and compare routes in the same region. If changing the quality fixes playback on every route, check your local network or playback device.

AI Tools

Check the provider's supported regions and account requirements first, then choose an exit that meets its rules. On the web, test signing in, submitting a prompt, and receiving the full response. If streaming output stalls, don't just refresh the page. Repeat the test with the same input and check whether there's no response at all or output starts and then stops; these point to different causes.

For API calls, distinguish network connection issues from usage limits and invalid credentials. Check the status code and error message before adjusting the timeout or comparing another route. If the platform explicitly reports a quota or concurrency limit, follow its guidance rather than treating a route change as the fix. For development use, see the AI Acceleration Guide.

Cross-Region Gaming

Choose based on the region of the actual game server, not the login page or publisher's location. Signing in only confirms that authentication works; it doesn't mean game traffic takes the same route. Compare short sessions on the same game server and watch for repeated rubber-banding, delayed actions, or disconnections.

If both route types lag when another device starts a large download, pause the transfer or test over a wired connection. Local congestion, Wi-Fi interference, and the cross-border path can all affect gameplay. If the game requires a dedicated acceleration method for its traffic, check the platform rules and whether the client is suitable for that use case.

Cross-Border Work

Choose a route in line with your organization's network and data policies. Web dashboards, file sync, and video meetings have different connection requirements, so test with your real workflow: open a document, upload a non-sensitive test file, and join a regular meeting. Being able to sign in doesn't mean saving, syncing, and meeting audio and video will all work reliably.

If your company's systems require a fixed exit or an administrator-managed allowlist, check with your administrator first. The region names and route types on this page don't indicate fixed IP addresses. Test your primary and backup routes before work begins. If a meeting drops, check your local connection and the platform's status before switching, so you don't interrupt an upload or unfinished edits.

First Month Free