REGIONAL REFERENCE
Route Options by Region
Country and city indicate the exit location; route type describes how traffic is carried. These are separate factors.
When choosing an international route, first narrow down the options to regions supported by the service you want to use, then compare routes within the same region. An exit location closer to you is often worth trying first, but geographic distance alone does not determine the actual route. Your local carrier, access network, international routing, and the destination website’s status can all affect the experience.
How to read this table: These examples show combinations of regions, cities, and route types to help explain the options. They are not a list of currently available servers, nor a guarantee that every listed city offers the route type shown. Check the user panel and client for available regions, cities, and route types. Streaming availability must be verified on the platform itself.
REFERENCE ONLY · Scroll horizontally on smaller screens to view the full table
| Country | City | Route type | Streaming availability |
|---|---|---|---|
| ASIA PACIFIC | |||
| China | Hong Kong | IEPL dedicated line (example) | Verify on the platform itself |
| Singapore | Singapore | Relayed (example) | Verify on the platform itself |
| Japan | Tokyo | IEPL dedicated line (example) | Verify on the platform itself |
| Japan | Osaka | Relayed (example) | Verify on the platform itself |
| South Korea | Seoul | Direct (example) | Verify on the platform itself |
| Australia | Sydney | Relayed (example) | Verify on the platform itself |
| NORTH AMERICA | |||
| United States | Los Angeles | IEPL dedicated line (example) | Verify on the platform itself |
| United States | Seattle | Relayed (example) | Verify on the platform itself |
| United States | New York | Direct (example) | Verify on the platform itself |
| Canada | Vancouver | Relayed (example) | Verify on the platform itself |
| Canada | Toronto | Direct (example) | Verify on the platform itself |
| EUROPE | |||
| United Kingdom | London | Relayed (example) | Verify on the platform itself |
| France | Paris | IEPL dedicated line (example) | Verify on the platform itself |
| Germany | Frankfurt | Relayed (example) | Verify on the platform itself |
| Netherlands | Amsterdam | Direct (example) | Verify on the platform itself |
| Sweden | Stockholm | Direct (example) | Verify on the platform itself |
| OTHER REGIONS | |||
| United Arab Emirates | Dubai | Relayed (example) | Verify on the platform itself |
| India | Mumbai | Direct (example) | Verify on the platform itself |
| Brazil | São Paulo | Relayed (example) | Verify on the platform itself |
| South Africa | Johannesburg | Direct (example) | Verify on the platform itself |
This page does not show live performance metrics. Coverage describes the service overall; it does not mean every route type is available in every country or city.
A region name does not guarantee access to content. Streaming platforms may check your exit IP, account region, and payment details separately; business systems may also check account permissions and device policies. Choosing the target region is only the first step—verify access on the service itself. A route name alone cannot guarantee that a service will work.
TRANSPORT TYPES
IEPL, Relayed, and Direct Connections: What’s the Difference?
The following describes how these route types generally work. It is not a performance guarantee for any specific route or a statement about separate charges.
IEPL Dedicated Lines
Managed international transit
IEPL generally refers to an international Ethernet private line. With this type of route, part of the international transit uses dedicated-line infrastructure rather than relying entirely on standard public internet routing. The distinction is how that transit segment is organized and managed; it does not mean the entire connection from your device to the destination website is exclusively reserved for you. Your local network, access segment, and the route from the exit to the destination service still affect performance.
For ongoing meetings, remote desktops, and long file transfers, an IEPL route shown in the client may be worth testing. Pay attention to interruptions, pauses, or reconnects over an extended session—not just how quickly a homepage loads. Consider evening performance in the context of your own internet connection.
Cost considerations: Dedicated-line resources typically involve transit capacity, carrier costs, and maintenance. They generally require higher infrastructure investment, but that does not mean VPNEJ charges separately by route. Check the plan and user panel for details on availability.
Relayed Connections
Separate entry and exit segments
A relayed connection adds a forwarding step between your device and the destination exit. The client first connects to an entry point, which then forwards traffic to the exit. Separating entry and exit can help adapt route combinations to different access networks, but the additional step means you also need to consider entry quality, onward transit, and exit status.
For everyday browsing, video streaming, and general access to online tools, a relayed route can be a good starting point for testing. If your local network connects more smoothly to a particular entry point, a relayed route may work better than one that appears more direct by name. Congestion at the entry point or along the onward route can also affect app performance. A relay by itself says nothing conclusive about speed or reliability.
Cost considerations: Relayed connections require resources for the entry point, forwarding, and exit. Costs depend on route design and capacity; they cannot be judged simply by counting the number of hops, nor do they imply a fixed performance ranking.
Direct Connections
Direct access to the destination exit
A direct connection generally means the client connects to an overseas exit without an additional relay entry point managed by the service. This describes how the connection is organized; it does not mean there are no routing devices in the physical network or that your local carrier will always choose the shortest path. Traffic still travels across carrier networks and international interconnections.
When the public internet route from your local network to the target region is suitable, a direct connection is worth keeping as a regular option or backup. If performance varies at certain times, compare it with other route types in the same region. If only one website is affected, check the service and client rules before concluding that all direct routes are unsuitable.
Cost considerations: Direct connections require fewer resources for additional relaying, but exit servers, network capacity, and operations still cost money. A simpler setup does not necessarily mean worse performance or a less expensive plan.
Consider routing and security separately. IEPL, relayed, and direct describe how traffic reaches an exit; military-grade encryption describes a security feature of the service. Route type alone does not tell you which encryption algorithm is used, what account permissions apply, or whether a destination platform will accept the connection.
WORKLOAD MATCHING
Choose a Cross-Border Route by Use Case
Start by defining what you need to do, then decide what to test. Different tasks do not have to use the same route.
BROWSING
Everyday Browsing
For documents, research, and web pages, check whether the page text, images, and static assets all load correctly. Start with an available route in a nearby region, then compare it on websites you use regularly. If the main page loads but images or attachments do not, check whether those assets use other domains and whether the client handles those requests as expected.
There is no need to switch exits frequently for browsing. Once you find a route that works well with your current network, keeping another route type as a backup usually makes it easier to identify problems than repeatedly changing regions.
STREAMING
Streaming and Video
First check which regions the platform serves, your account’s subscription permissions, and the catalog where the title is available. Then choose an exit in the relevant region. Loading the platform does not mean a video will play, and seeing a title in search results does not mean your account can watch it. Sign in to your own account, open the specific title, and check playback and available video quality.
Playback interruptions may also be caused by local Wi-Fi, background transfers, or device decoding. When comparing routes, keep the video and device the same rather than changing every variable at once. Content permissions and regional detection can change; a route name is no guarantee of ongoing access. For a fuller explanation of regional checks, see the Streaming Guide.
AI TOOLS
AI Tools
Before using AI tools such as ChatGPT, check the platform’s supported regions, your account status, and its applicable usage rules. Once you have selected an exit in a supported region, try to keep the session in that region. Account sign-in, web chats, file uploads, and API requests may use different domains, so check that the client’s routing rules apply to each one.
When access fails, distinguish between a region notice, account verification, rate limits, and a network connection error. A network route can affect connectivity, but it cannot grant platform access or restore a suspended account. For further troubleshooting, see the AI Tools Guide; not every error is caused by a server location.
GAMING
Gaming
First check your game region and the location of the actual matchmaking servers. A working login page does not mean gameplay traffic is using the expected route; some games use different connection methods, so compatibility needs to be tested. Follow the game’s rules and start with an exit suited to the target region.
Check login, joining a lobby, and sustained gameplay—not just game downloads. Updates and cloud sync can use your local network, so check their status before testing. The route categories on this page are not dedicated gaming services and do not guarantee compatibility with every game.
REMOTE WORK
Work and Collaboration
Remote meetings, business documents, and code collaboration depend on sustained sessions and consistent account regions. Check your organization’s network policies first, then choose a route that supports your work over time. If your company system uses an allowlist of exit IPs, confirm the requirements with your administrator; a country or city name does not guarantee a fixed exit IP address.
You can test meetings, file uploads, and remote desktops separately, noting which tasks work on each route type. If something fails, keep the app’s error message and client status so support staff can distinguish local network, route selection, and business account permission issues. Unlimited devices is a device-use allowance; it does not mean each device gets dedicated network capacity when several devices are transferring data at once.
CONNECTION CHECK
Verify the Connection After Choosing a Route
Keep test conditions comparable. Change one factor at a time to make results easier to reproduce.
From Client Connection to Real-World Tasks
- Check your current setup. Sign in to the user panel, confirm your subscription status, and update the route configuration in your client. Choose a region and route using the names shown in the panel; do not treat this reference table as a list of available options. For client downloads and setup, see the Getting Started Guide.
- Check your local connection. First make sure your regular internet access is working, then confirm that the client is operating as expected. If your device has another proxy or workplace access tool, follow its instructions to avoid conflicting configurations.
- Test the task you need. For web access, check page text and attachments; for streaming, test playback; for work, check sessions and file operations. Testing one public website does not prove that other apps use the same route.
- Compare routes methodically. Keep the destination service, account, and device unchanged, and first compare different routes in the same region. If you need to change regions, recheck the platform’s regional requirements. Results from different times or networks should not be treated as fixed properties of a route.
- Keep troubleshooting details. Note the platform, route name, app error, and steps to reproduce the issue, then submit them through a user panel support ticket. Hide account details and subscription links when describing a problem; do not send passwords or full access credentials.
ACCESS
Platforms and Accounts
Supports Windows / macOS / iOS / Android / Linux, with unlimited concurrent devices. No email address required—create an account with a username and password. Get the client and subscription details through the user panel; available route configurations are those shown in your account.
Get the Client →BILLING
Plans and Usage
Monthly subscription data resets each month on the activation date. If you upgrade mid-cycle, the price difference is converted into remaining days. Data packages remain available until used and never expire. Check plan data allowances against your usual tasks before choosing. 14-day no-questions-asked refunds. Check the panel for currently available routes.
View Plans →