Choose a region first, then compare route types. VPNUB covers 90+ countries / 220+ routes. Available servers are listed in the client after logging in.
Create an account with a username and password—no email address required.
Browse routes by region
Review the examples, then check the client
The table below illustrates how route options are organized; it is not a current availability list. Cities and route types show how to read server names. They do not mean that every combination is always available or that a particular streaming catalog has been tested. Check the client for current servers, exit locations, and available route types.
Streaming availability is not labeled as universally “supported.” Results can vary by platform, catalog, exit IP recognition, and account requirements—even within the same region. Test playback on the platform itself; a region name alone is not enough to draw conclusions.
How to read regions and route types
Country / region
City
Route type
Streaming availability
Asia-Pacific
Singapore
Singapore
IEPL
Check on the platform and in the region
Japan
Tokyo
Relay
Check on the platform and in the region
Hong Kong
Hong Kong
IEPL
Check on the platform and in the region
Japan
Osaka
Direct
Check on the platform and in the region
South Korea
Seoul
Relay
Check on the platform and in the region
Australia
Sydney
Relay
Check on the platform and in the region
New Zealand
Auckland
Direct
Check on the platform and in the region
North America
United States
Los Angeles
Relay
Check on the platform and in the region
United States
New York
Relay
Check on the platform and in the region
Canada
Vancouver
Direct
Check on the platform and in the region
Canada
Toronto
Relay
Check on the platform and in the region
Europe
United Kingdom
London
Relay
Check on the platform and in the region
Germany
Frankfurt
IEPL
Check on the platform and in the region
France
Paris
Relay
Check on the platform and in the region
Netherlands
Amsterdam
Direct
Check on the platform and in the region
Switzerland
Zurich
Relay
Check on the platform and in the region
Other regions
Brazil
São Paulo
Relay
Check on the platform and in the region
South Africa
Johannesburg
Relay
Check on the platform and in the region
United Arab Emirates
Dubai
Relay
Check on the platform and in the region
Turkey
Istanbul
Direct
Check on the platform and in the region
On narrow screens, scroll the table horizontally. The city in a server name identifies its exit location; it does not mean traffic travels only through that city between you and the destination website.
Route types mainly describe how a connection reaches its exit; they do not determine whether a website will work. Consider the transmission path, exit region, and target platform’s rules separately. The same route type can perform differently across local networks and at different times.
Dedicated routing
IEPL
For situations where consistent connection performance matters.
IEPL generally refers to an international Ethernet private line. It carries cross-border traffic over a dedicated segment, rather than relying directly on public internet routes for that segment. “Dedicated line” describes only the relevant part of the transmission path—not the entire connection from your device to the destination website. Local access, the exit network, and the website itself can all affect the result.
For video calls, remote work, or extended streaming sessions, compare routes explicitly labeled IEPL in the client. Focus on whether sessions stay connected, page requests are interrupted, and performance during your usual hours meets your needs. The route name alone does not guarantee a set speed or streaming availability.
Dedicated lines typically involve additional transmission and maintenance costs. Higher costs do not mean every app will be faster. VPNUB plan prices are listed on the plans page; this page does not assign separate fees to route types or claim that a particular plan includes dedicated resources.
Entry-point forwarding
Relay
Useful for comparing combinations of entry points and onward routes.
A relay adds a forwarding entry point between your device and the final exit. Your device connects to the entry point first, then subsequent networks carry traffic to the exit. The entry point and exit region may differ. Platforms generally determine your access region from the final exit, not the entry point’s name.
When the direct route from your local network to an exit performs poorly, a relay offers an alternative route combination. It may improve the connection, but congestion at the entry point or changes along the onward route can also affect performance. An extra forwarding step does not automatically make a connection slower, and “relay” does not mean it is always better than direct.
Relays require resources to maintain connections between entry points and exits. Costs vary with the route, carriers, and capacity. Compare real-world app performance for the same exit region first. Changing both the region and route type at once makes it harder to identify what affected the result. Test the combinations available in the client; a more complex route name is not necessarily better.
Direct connection
Direct
A good fit when the route from your local network to the exit performs well.
Direct usually means the client connects to the selected exit service without an additional relay entry point provided by this service. Traffic still passes through your local carrier and internet routing; there is no physically direct link between your device and the exit. A shorter geographic distance does not necessarily mean a shorter network route.
For everyday browsing, research, and lightweight apps, start by testing an available direct route. If pages load smoothly and sessions remain stable, there is no need to switch just because another route type is available. If performance changes in the evening, compare relay or IEPL options in the same region and keep the combination that works best on your network.
Direct routing has a relatively simple structure and typically uses fewer additional relay resources, though operating costs still depend on the exit and network procurement. A simple setup does not imply a different privacy policy, and route type alone does not indicate a dedicated IP, residential IP, or eligibility for a particular platform. Those attributes must be stated separately; they cannot be inferred from the route name.
Region, route type, and IP attributes are different things. IEPL does not mean residential IP, relay does not mean dedicated IP, and direct does not guarantee access to any particular platform.
Choose a route for your use case
Let the target app guide your choice
Everyday browsing
First check that pages load consistently
For reading websites, researching, or email, start with an exit region that meets the service’s requirements and connects reliably on your local network. Test more than the home page: open articles, attachments, and images to check that page resources load too. If the home page appears but the article stalls, split-tunneling rules or separate resource domains may be involved; it does not necessarily mean the entire route is down.
If a site has no specific regional requirements, start by comparing nearby exits, then keep the one that works best. Distance is a starting point, not a verdict. After switching routes, reload the page so you do not mistake browser cache for the new route’s performance.
Streaming
Check the catalog, then test playback
Before streaming, identify the platform and catalog region you want, then choose the corresponding exit. Platforms such as Netflix and Disney+ may consider exit IP recognition, account region, payment details, and content licensing. Reaching the home page or seeing a title poster does not mean the video will play. Open the title and check playback, subtitles, and buffering over time.
If playback fails, note the platform’s message and check your account plan and regional requirements before trying another route in the same region. Avoid repeatedly switching regions at random; it makes cache and session state harder to assess. Picture quality also depends on your device, app, content version, and local network—route region alone cannot guarantee it.
Check regional eligibility separately from connectivity
Before using AI tools such as Claude, check the platform’s published service regions and account requirements, then choose an eligible exit. A network connection changes the access path; it does not change account eligibility or platform terms. Opening an information page does not guarantee that sign-in, chat, and file uploads will follow the same request path.
Test the actual workflow by signing in, submitting a prompt, and reviewing the response. If the site opens but chat does not respond, check whether the client’s routing rules cover the relevant requests and note any app messages. Keep the exit region consistent during work where possible. If you see a verification prompt, follow the platform’s process rather than assuming every account issue is caused by the route.
Gaming
Match the game server, not just the route type
First confirm the region of the server your game actually connects to. Account region, store region, and match server may differ, so do not choose an exit based only on the store page. After signing in, check the lobby, matchmaking, and gameplay, since each stage may connect to different services.
Gaming depends on consistent responsiveness and route stability; smooth web browsing is no substitute for testing in a match. VPNUB is a cross-border network acceleration service and does not promise compatibility with specific games on this page. Follow the game’s permitted connection methods and check whether the client routes that app. Simply changing servers usually will not help if the app’s traffic is not using the selected route.
Remote work
Keep your session and work exit consistent
For work, follow your organization’s network and data-handling requirements first. If access to company resources depends on an approved exit, check with your administrator rather than assuming a different region will grant access. Test video calls, remote desktops, and document collaboration separately; smooth file transfers do not guarantee uninterrupted calls.
Test during your actual working hours and settle on a route before important meetings or file uploads. Switching exits frequently during a long session may require you to sign in again or reconnect. VPNUB supports unlimited devices, but keep an eye on plan data when devices share a subscription. Monthly subscription data resets each month on the activation date; data add-ons remain available until used and never expire.
Verification after connecting
Check device status, then test the app
Confirm the app is using your selected exit
First check the route name and connection status shown in the client, then check your current exit details. If other proxy or networking tools are running on the device, see whether they affect system routing. A connected status means a connection has been established; it does not automatically prove that every app uses it.
With split-tunneling rules, different apps or websites may use different routes. An exit lookup can provide a clue, but you still need to test in the target app. Record the device platform, route name, where the error occurs, and any message shown. This is more useful for troubleshooting than simply saying “it doesn’t work.”
When comparing routes, keep the device, local network, and target app the same, and change only the route you are testing. After switching, wait for the client to reconnect before sending a new request. If you also change the local network, exit region, and client mode, it is difficult to tell which change made a difference.
If you cannot identify the cause, submit a support ticket through the dashboard with the route name and error details. Before sharing screenshots, hide your account password and subscription information. New users can follow the getting started guide to configure the client. The service offers a 7-day refund policy; see the Terms of Service for eligibility details.