Choose an exit region first, then compare connection paths. The country identifies the exit location; IEPL, relayed and direct describe how the connection gets there.
No email required · Unlimited devices · 30-day money-back guarantee
Browse routes by region
Start with the region where the service you need is based. City and route combinations across Asia-Pacific, North America, Europe and other regions help explain the information shown in route names.
Examples for comparing routes—not a live server list
The table illustrates how to read common regions, cities and route types; it does not mean every combination is currently available. Check the account dashboard for available cities, route types and exit locations. Streaming availability is not guaranteed across the board; verify it against the platform, content region and your own results.
Examples of regions, cities and route types
Country / region
City
Route type
Streaming availability
Asia-Pacific
Hong Kong, China
Hong Kong
IEPL
Check by platform and content region
Japan
Tokyo
Relayed
Check by platform and content region
Singapore
Singapore
IEPL
Check by platform and content region
South Korea
Seoul
Direct
Check by platform and content region
Australia
Sydney
Relayed
Check by platform and content region
North America
United States
Los Angeles
Relayed
Check by platform and content region
United States
Seattle
Direct
Check by platform and content region
United States
New York
Relayed
Check by platform and content region
Canada
Vancouver
Direct
Check by platform and content region
Canada
Toronto
Relayed
Check by platform and content region
Europe
United Kingdom
London
Relayed
Check by platform and content region
Germany
Frankfurt
IEPL
Check by platform and content region
France
Paris
Direct
Check by platform and content region
Netherlands
Amsterdam
Relayed
Check by platform and content region
Sweden
Stockholm
Direct
Check by platform and content region
Other regions
United Arab Emirates
Dubai
Relayed
Check by platform and content region
Brazil
São Paulo
Relayed
Check by platform and content region
South Africa
Johannesburg
Direct
Check by platform and content region
India
Mumbai
Relayed
Check by platform and content region
New Zealand
Auckland
Direct
Check by platform and content region
Exit city does not indicate your entry location
A city name usually identifies the exit location. It does not mean your device connects via the geographically shortest route. Traffic also travels from the exit to the destination service. Even when two routes are both labeled Tokyo, their entry points, carrier interconnections and forwarding paths may differ. Judge them by how they perform in your applications, not by distance on a map.
Same region, different content availability
Streaming catalogs can depend on your account region, content licensing, how the exit IP is identified and app settings. Loading a platform’s home page does not mean a specific title will play; successful playback does not guarantee a particular resolution. If you need content from a specific region, check the account and content requirements, then test the relevant exit. See our guide to streaming access for ways to check.
IEPL, relayed and direct routes
These terms describe connection paths, not speed tiers. The explanations below are general; check the route details in your account dashboard for the actual setup and available protocols.
IEPL
Understand cross-region routes →
For situations where a consistent connection matters.
IEPL usually refers to an international Ethernet private line. Route operators can use dedicated cross-region transport resources to connect entry and exit points, reducing reliance on some public peering paths. Its value lies in the transport path and resource allocation; it does not make every connection between your device and every website a private channel. Your home network, access provider and the route from the exit to the destination website can all affect the experience.
Video calls, remote desktops and sustained transfers are more sensitive to connection fluctuations than to peak download speeds, making IEPL routes worth comparing. Dedicated transport resources often cost more to procure and maintain, but the name alone does not tell you whether a plan costs more or will be faster. This page does not tie route types to specific prices; check which routes are actually available in your account dashboard.
Relayed
Reach an international exit via an entry point →
For comparing connection performance across different paths.
With a relayed route, your device connects to an entry point first, which then forwards traffic to the exit. An extra forwarding step does not necessarily make a connection worse: if the path between entry and exit is more suitable, the overall connection may be steadier than a direct connection from your device to the exit. On the other hand, congestion at the entry point or along the relay path can affect performance. Assess the full path rather than counting the number of hops.
Relayed routes can work for everyday browsing, online documents and streaming. Costs may include entry resources, forwarded traffic and exit resources; the exact difference depends on how those resources are procured, so there is no universal ranking. If things slow down in the evening, keep the exit region the same and compare another entry point or topology. This can help isolate the issue better than repeatedly changing countries.
Direct
Connect directly to the exit →
A useful baseline for comparing paths and troubleshooting.
A direct route generally means your device connects to the exit server without a separate relay entry point. The setup is relatively simple, but cross-region traffic still depends on networks along the way and how carriers interconnect. “Direct” describes the connection arrangement; it does not mean the geographic route is shortest or eliminate the effects of your local access network. The same exit can perform differently on home broadband and mobile networks.
A direct route can be an option for everyday use and a useful comparison against relayed routes when troubleshooting. It may avoid the cost of additional forwarding resources, but the exit location and network procurement conditions matter too, so you cannot infer a fixed price difference. If a direct route works for your application, there is no need to switch to a more complex path just for its name. If performance is inconsistent, compare other topologies.
Choose an exit by use case
First identify the region, connection type and consistency your application needs, then compare suitable routes. A route that consistently gets the job done is more useful than one that only looks faster in a single test.
Everyday browsing →
Check that pages load fully before focusing on region.
For reading websites, researching and viewing images, start with a nearby exit available in your dashboard, but do not use proximity as your only criterion. Open your usual sites and check whether images, sign-in and embedded content all load. If only one site has an issue, check your routing rules and the site’s status before switching all traffic. Once you find a route that works well, keep another route with a different path as a backup.
Streaming →
Match the content region first, then test playback.
For streaming, check the region requirements for the platform and title, then choose an exit. Test the title itself rather than stopping at the home page or search results. If the catalog looks right but playback keeps buffering, compare other routes in the same region and check your local Wi-Fi and background transfers. Video quality also depends on your platform plan, device capabilities and the content itself; neither region nor route type guarantees a particular resolution.
AI tools →
Keep to a suitable region and test the full task.
For AI chat, coding assistance or file analysis, first check the tool’s supported regions and account requirements. Choose an appropriate exit, then test sign-in, response generation, file uploads and longer tasks. Frequently changing regions in a short period may trigger additional account checks, so keep the region relatively consistent once you confirm the route works. If the website works but the desktop app does not, check the app’s proxy settings. See our guide to network acceleration for AI tools.
Gaming →
Check against the game server’s region.
Gaming performance depends on the full path from your device to the game server; exit location or route name alone cannot tell you how well it will work. First check the game’s server region, then confirm that your client’s proxy mode covers the game process and supports the game’s traffic type. Accessing a website in a browser does not mean game traffic uses the same path. Follow the game’s terms of service and assess performance in actual matches; general network acceleration is not the same as game-specific optimization.
Remote work →
Prioritize calls, documents and session continuity.
For work, follow your organization’s access requirements first and avoid conflicts between internal business networks and personal proxy settings. Test video and audio calls, shared documents, file transfers and remote desktops separately; a web page loading is not a substitute for testing everything. Avoid switching exits in the middle of a call or while editing an online document, as the connection may reset and interrupt your session. Confirm your usual route and a backup before starting work. If an issue comes up, save your work before switching.
Connection checks, step by step
Check “connected” separately from “the target app works.” During troubleshooting, change one condition at a time so you can identify where the issue lies.
Check the exit first, then the app
After connecting, use an IP lookup to check your browser’s current exit, then open the service you actually need. The lookup only shows the browser’s route; it cannot confirm that every app is using the proxy. If the browser exit has changed but a desktop app still has issues, check system proxy settings, app-specific settings and routing rules. If the reported region differs from the route label, the IP geolocation database may need updating; compare it with the information in your account dashboard.
Keep the region; compare the paths
If a service requires a specific region, compare different routes within that region first. Avoid changing the region, protocol and proxy mode at the same time. If another route in the same region works, the original path may be the issue. If the same app fails across several exits, check the app, account or destination service. Comparing your home network with another access network can also help, but check the exit again after switching networks so you do not mistake a local network difference for a route change.
Note what happened, then contact support
If you need help, submit a ticket through your account dashboard and include the platform, route name, destination service and the step where the issue occurs. For example, distinguish between a connection failure, missing page resources, an interrupted sign-in or buffering; this is more useful than simply saying “it’s slow.” Before sharing a screenshot, hide your subscription URL, password and other account details. Follow the setup guide to check the full process for getting a client, importing a subscription and connecting for the first time.