International Routes · Server Directory

Global Server Locations

Start by choosing an exit region that works for your target service, then compare route types. The same region can involve different network paths. Test a shortlisted route with your actual use case rather than choosing by city name alone.

Browse routes by region

The table below shows how to filter by city and route type; it is not a list of currently available servers. The streaming column distinguishes use-case examples from items that need verification. Unverified does not mean unsupported, and support cannot be determined from a city or route type alone.

Country or region, exit city, route type, and streaming suitability
Country / RegionCityRoute typeStreaming support
Asia-Pacific
ChinaHong KongIEPLNetflix use-case example; verify availability
SingaporeSingaporeRelayNeeds verification
JapanTokyoDirectNeeds verification
JapanOsakaRelayNeeds verification
South KoreaSeoulDirectNeeds verification
AustraliaSydneyDirectNeeds verification
North America
United StatesLos AngelesDirectNeeds verification
United StatesSeattleRelayNeeds verification
United StatesNew YorkDirectNeeds verification
CanadaVancouverRelayNeeds verification
CanadaTorontoDirectNeeds verification
Europe
GermanyFrankfurtDirectNeeds verification
United KingdomLondonRelayNeeds verification
FranceParisDirectNeeds verification
NetherlandsAmsterdamRelayNeeds verification
SwedenStockholmDirectNeeds verification
Other regions
BrazilSão PauloRelayNeeds verification
ChileSantiagoDirectNeeds verification
United Arab EmiratesDubaiRelayNeeds verification
South AfricaJohannesburgDirectNeeds verification

In the app, use a city as a starting point for choosing an exit location; it does not mean the local access point is in that same city. If a city is missing, update your subscription first, then check for another exit in the same country or region. If your target service requires a specific region, do not switch to an unsuitable region just to choose a closer city.

Route types and cost differences

Route types describe how traffic travels. They do not indicate whether an exit is dedicated or specify a protocol. Connection quality also depends on local access, cross-border transport, and the path from the exit to the target service. For a fair comparison, use the same exit region and assess route differences separately from regional differences.

IEPL

Local access → Dedicated connection → Exit

IEPL stands for International Ethernet Private Line. When used for cross-border transport, the dedicated segment connects access points at both ends, and the operator can manage its capacity and delivery under an agreement. It describes only one part of the route: network congestion can still affect the connection from your device to the access point and from the exit to the target service.

A useful option to compare during your usual hours for video calls, remote desktops, or long transfers. Dedicated lines typically involve circuit leases, capacity planning, and maintenance, so setup and operating costs are often higher than using the public internet directly. For occasional browsing, first see whether an existing route does the job before deciding whether a dedicated path offers practical value.

Relay

Local access → Relay node → Exit

Relay routes separate the entry point from the exit. Traffic first reaches a relay node, then travels over another network segment to the exit. If your local carrier has a better connection to the relay entry point, the route may be more stable than going directly to the exit, even with an extra hop. On the other hand, queues at the relay entry or detours on the next segment can slow the entire connection.

If a direct route in the same region often stalls during peak hours, try a relay route for comparison without changing the exit first. Relays generally require additional entry resources and forwarding links, and costs depend on how access and exit capacity work together. A relay is a routing arrangement, not a fixed performance tier, and does not imply a particular plan price.

Direct

Local access → Exit

Direct means the service does not add a separate relay entry point; the app connects straight to the exit node. Traffic still passes through local carrier and public-network routers, and the actual route may not follow the shortest distance on a map. Direct routes typically have one fewer service-managed forwarding step and a simpler resource setup, but carrier interconnection and exit capacity still have costs.

A good baseline for browsing, document syncing, and similar tasks. If pages load normally and the connection does not keep reconnecting on your usual network and schedule, there is no need to switch to a more complex route based on its name alone. If issues start only after changing access networks, compare route types while keeping the same exit.

Choose a route for your use case

Keep the same device, access network, and target service during testing; change only one variable at a time. Note what actually happens: whether pages load fully, playback is interrupted, or sessions reconnect. Identify the problem area before deciding whether to change regions or route types.

Everyday browsing

If the site does not require a specific region, start with a direct route in a nearby region. Open international sites you use regularly and check more than the landing page: open an image-heavy detail page, navigate to another page, or run a site search. A page title appearing while images remain blank is different from the whole site being unreachable. If only one site has issues, compare with another before changing all your settings.

If you regularly switch between home and office networks, save a suitable option for each. A route that works well on one network may not be the best choice with another carrier. In practice, reliable access to your frequently visited sites is more useful than one unusually fast page load.

Streaming

Choose an exit based on the catalog you want, your account region, and the platform's rules; then check whether the app labels a route for that platform. Being able to open Netflix, Disney+, or YouTube does not guarantee that the content you want will play on your account. Sign in with your own account, start the program, and seek through it to check whether playback recovers after buffering and whether subtitles and video quality switch as expected.

If you see a region warning, first check your account and the program's availability. If playback keeps buffering, keep the region unchanged and compare other routes with the same program during your usual viewing hours. Avoid changing video quality, device, or Wi-Fi location at the same time; otherwise, it is hard to tell whether the issue comes from the route, device, or local connection.

AI tools

For tools such as ChatGPT and Claude, first check account requirements and the regions supported by the platform. Opening the site is only a first step: check whether responses keep coming, long answers arrive in full, and an allowed test file uploads successfully. Avoid switching exit regions repeatedly while troubleshooting, so changes to your account session do not get mixed up with route tests.

For API calls, identify the step where the error occurs. If the request times out before receiving a response, compare the same request over another route. If the service returns a quota, authentication, or request-format error, check your account and parameters first. A working website does not replace an API test; the two may use different destinations and request durations.

Online gaming

Choose an exit based on the game region you actually play on, not just the city closest to your device. First confirm that the game and app are compatible with the network mode, especially if the game relies on UDP. Join a match in the same region and check for inconsistent input response, sudden character rollbacks, and whether you can reconnect after a disconnection. A successful login only confirms that the login process worked; it does not mean gameplay will be just as smooth.

Pause background downloads while troubleshooting and keep your access method consistent. If several game regions show similar lag, check your local Wi-Fi and background traffic first. If the problem occurs in only one region, compare direct and relay routes to that region. A smooth game update download is not a substitute for testing a match.

Remote work

Test your actual workflow: join a meeting, check two-way audio, share your screen, then transfer a test file with no sensitive information. For meeting audio, listen for dropped words; for screen sharing, check that updates appear continuously; for remote desktops, see whether keyboard actions and visual feedback stay in sync. A one-way download test cannot assess these two-way tasks.

If your organization requires a specific exit or access method, follow its policies first. When you need a backup route, prioritize testing whether another path in the same region can handle the same task. If possible, switch outside meetings or file transfers. After an interruption, note the time, app, and steps that triggered it so you can reproduce the same conditions next time.

Try it free