Choose a region, then pick a route type. InnVPN covers 90+ countries / 250+ routes. Sign in to see the options currently available to you.
Learn how regions, exit locations, and route types fit together. This directory is for reference, not a live availability list. Check the actual connection to see whether it works for your target site.
Browse routes by location
The table shows how to read the regions, cities, and route types. City names indicate possible exit locations, but a target site may identify the exit differently. Check the user panel and the latest client list for currently available regions, names, and types.
On smaller screens, swipe horizontally within the table to view cities, route types, and streaming notes.
Regional routes · Example names and types, not a fixed availability list
Country / Region
City
Route type
Streaming availability
Asia-Pacific
Hong Kong, China
Hong Kong
IEPL
Verify for yourself
Singapore
Singapore
Relay
Verify for yourself
Japan
Tokyo
Relay
Verify for yourself
Japan
Osaka
Direct
Verify for yourself
South Korea
Seoul
Relay
Verify for yourself
Australia
Sydney
Direct
Verify for yourself
New Zealand
Auckland
Direct
Verify for yourself
Malaysia
Kuala Lumpur
Relay
Verify for yourself
North America
United States
Los Angeles
Relay
Verify for yourself
United States
Seattle
Direct
Verify for yourself
Canada
Toronto
Relay
Verify for yourself
Canada
Vancouver
Direct
Verify for yourself
Europe
France
Paris
Relay
Verify for yourself
United Kingdom
London
Relay
Verify for yourself
Germany
Frankfurt
Direct
Verify for yourself
Netherlands
Amsterdam
Relay
Verify for yourself
Switzerland
Zurich
Direct
Verify for yourself
Sweden
Stockholm
Direct
Verify for yourself
Other regions
Brazil
São Paulo
Relay
Verify for yourself
Chile
Santiago
Direct
Verify for yourself
South Africa
Johannesburg
Relay
Verify for yourself
United Arab Emirates
Dubai
Direct
Verify for yourself
This table does not show every covered region. If you can’t find the exit you need, update your subscription and check the route details in the panel. Don’t rely on old screenshots to determine current availability.
These terms describe network paths, not app permissions. Route type alone can’t determine whether a site will work, and it doesn’t replace checking your local network, target region, and client rules. The explanations below cover general principles; not every type is available in every region.
Dedicated transit
IEPL
A managed cross-region transport segment
IEPL usually refers to an international Ethernet private line. In common subscription service architectures, it carries part of the traffic between an entry point and an overseas exit, reducing reliance on ordinary cross-region public internet paths. The local connection from your device to the entry point and the onward connection from the exit to the target site still affect your experience. A “dedicated line” label does not mean every segment uses a private network.
This type of path may be worth testing for sustained traffic, such as long streaming sessions, video calls, or extended tool sessions. If connections become unreliable in the evening, compare an IEPL route with other types in the same region, but don’t judge by the label alone. Dedicated transit resources generally cost more to deploy and maintain; that doesn’t make them a better fit for every use. See the plans page for InnVPN pricing.
Relay routing
Relay
Connect to an exit through an intermediate entry point
With a relay route, your device connects to an entry point first, which then forwards traffic to the selected exit. This allows for more flexibility in routing and may help when a direct connection between your local network and an overseas exit performs poorly. The region shown in the client usually refers to the final exit, not necessarily the entry point. To know what region a target site sees, check the actual exit after connecting rather than relying on the entry name.
Relay routes are one option for everyday browsing, research, and accessing tools. They use resources for the entry point, forwarding, and exit, and require coordination across the route. That doesn’t mean an extra hop is always slower—or always better. If a relay route performs poorly, compare another route in the same region while keeping the target site and usage the same.
Public internet path
Direct
Connect directly from your device to a remote exit
A direct route typically connects your device to a remote server over your current network, without an additional relay entry point set up by the service. The path is simpler to understand and involves fewer deployment steps, but traffic still travels through carrier networks. A nearby location doesn’t necessarily mean a short network path; peering between carriers, routing, and current network conditions can all affect performance.
If your local network already connects well to the target region, a direct route may work for browsing, work, or as a backup. It generally uses fewer relay resources, but that doesn’t mean the plan will cost less or that the connection will outperform a relay. Compare page loads, sustained transfers, and reconnection behavior for the same use case rather than ranking routes by name alone.
Choose a route by use case
Start by defining what you need to do, then choose an exit. The same route can behave differently across apps, and successfully loading a web page doesn’t verify streaming, uploads, or persistent connections.
Web and research
Everyday browsing
If you don’t need a specific region, start with a nearby location that’s available in your panel. Open a site you use regularly and check that text, images, and sign-in all work. If the homepage loads but other pages don’t, check whether their resources follow the same routing rules before assuming the exit region is the problem.
For everyday use, keep a suitable regular exit and set up another route as a backup. Switching countries repeatedly in a short time makes troubleshooting harder and may trigger account security checks. If you use smart routing, confirm that the target site matches a proxy rule.
Streaming and regions
Streaming
Check the video platform’s account-region and content-region requirements first, then choose an appropriate exit. A route’s country name doesn’t determine content rights; the same title may appear differently depending on your account, app version, or platform policies. After connecting, open the specific content you want to watch and check whether playback starts and continues without repeated buffering.
After switching exits, an app may still retain information about the previous region. Leave the playback screen, reopen the app, and check the route currently selected in your client. If a region notice still appears, note its exact wording and test another exit in the same region. See the streaming guide for more troubleshooting tips. Don’t treat the directory as a list of guaranteed supported regions.
Chat and development
AI Tools
Each AI service sets its own supported regions and account eligibility. Check the service’s rules first, then choose an exit that meets its requirements; a network route can’t replace account permissions. For browser-based chats, check that full responses keep loading. For editors and command-line tools, check their proxy settings separately, as they may not use the browser’s connection.
For long sessions, keep the same exit where possible. If your browser works but an editor can’t connect, check the system proxy, terminal environment, and the tool’s own settings before switching countries repeatedly. Note conversation interruptions, failed attachment uploads, and account notices separately. For troubleshooting steps, see the ChatGPT connectivity guide.
Interactive connections
Gaming
Check which region the game server is in and whether the game permits the network setup you plan to use. A subscription network service isn’t the same as a dedicated product optimized for a particular game. Accessing the game platform or downloading updates doesn’t confirm that gameplay, voice chat, and matchmaking use the same route, and download performance alone doesn’t predict the interactive experience.
When testing, check sign-in, updates, voice chat, and gameplay separately. If only one feature has a problem, check whether your client supports that traffic type and whether the game process matches a proxy rule. Don’t assume an exit is suitable just because its city is near the server. Test it in practice while following the platform’s rules.
Meetings and collaboration
Work
For work, follow your organization’s network and data requirements first. If your company has a dedicated access method, ask your administrator whether other network services can be used alongside it. A cloud document loading doesn’t mean meetings, file uploads, and internal systems use the same connection. Test each feature you need before relying on it for important work.
InnVPN supports unlimited devices, but results can still differ between devices due to operating system permissions, network conditions, or client rules. If one device has a problem, check its subscription and current exit on that device rather than relying on another device’s successful connection. For ongoing work, keep a verified route available and note your original settings before making changes so you can restore them.
Connection checklist
Confirm separately that the route is selected and that the app is actually using it. Change just one thing at a time while troubleshooting to pinpoint whether the issue is the local network, client rules, exit, or target service.
Check your subscription and exit
Sign in to the panel to check your plan and subscription status, then update the subscription in your client. Make sure the route you intend to test is selected, and check that smart routing, global, or direct mode matches your use case. If route names change after an update, use the latest list rather than relying on old saved entries.
Monthly subscription data resets each month on the activation date. Data add-ons remain available until used and never expire. If you’re having connection problems, check your remaining data as well as whether the route still appears in the list. To compare data allowances and prices, see the plan details.
Test the specific app
Open the target site or app and repeat the task you actually need to complete. If only one app fails, first check its proxy settings, cache, and account notices. If multiple targets fail, compare another route in the same region. Keep the device and network connection unchanged during testing so you don’t alter too many variables at once.
If you still can’t identify the issue, note the client name, operating system, selected region, route type, time of the issue, and error message, then submit them through the support ticket portal. Hide passwords, subscription details, and other account information in screenshots. For the full troubleshooting process, see Troubleshooting.