Start with your target location, then consider the route type. The right connection depends on the sites, tools and work hours that matter to you.
Coverage
110+ countries / 190+ routes
Concurrent devices
Unlimited devices
Refund policy
14-day no-questions-asked refund
This page explains locations and route selection; it does not provide live performance metrics. Check the user panel for currently available routes, city names and route types.
REGIONAL REFERENCE
Browse routes by location
A country or region indicates the approximate exit location; the city helps distinguish entry points within that location. The table shows examples of locations and route types. It does not mean every combination is always available, and it is not a complete list of available servers.
On narrow screens, swipe horizontally to view cities, route types and streaming notes.
Location and route type guide · Check the user panel for current availability
Country / region
City
Route type
Streaming availability
Asia-Pacific
Hong Kong, China
Hong Kong
IEPL
Depends on testing with the target platform
Singapore
Singapore
Relayed
Depends on testing with the target platform
Japan
Tokyo
IEPL
Depends on testing with the target platform
South Korea
Seoul
Relayed
Depends on testing with the target platform
Taiwan
Taipei
Relayed
Depends on testing with the target platform
Australia
Sydney
Direct
Depends on testing with the target platform
New Zealand
Auckland
Relayed
Depends on testing with the target platform
North America
United States
Los Angeles
Direct
Depends on testing with the target platform
Canada
Vancouver
Relayed
Depends on testing with the target platform
Europe
United Kingdom
London
Relayed
Depends on testing with the target platform
Germany
Frankfurt
Direct
Depends on testing with the target platform
France
Paris
Relayed
Depends on testing with the target platform
Netherlands
Amsterdam
Direct
Depends on testing with the target platform
Switzerland
Zurich
Relayed
Depends on testing with the target platform
Sweden
Stockholm
Relayed
Depends on testing with the target platform
Ireland
Dublin
Direct
Depends on testing with the target platform
Italy
Milan
Relayed
Depends on testing with the target platform
Other regions
United Arab Emirates
Dubai
Relayed
Depends on testing with the target platform
Brazil
São Paulo
Relayed
Depends on testing with the target platform
South Africa
Johannesburg
Relayed
Depends on testing with the target platform
Coverage versus currently available routes
ShunVPN covers 110+ countries and 190+ routes. Coverage describes the service's overall reach; it does not mean every location has the same number of exit points or that every route type is available in every city. Use the current list in the user panel to choose a connection. If an example on this page differs from a name in the panel, follow the panel and avoid repeatedly importing an old subscription to find names that may have changed.
A location choice does not guarantee that a target website permits access. A site may determine eligibility based on account region, billing details, local rules and exit address. Review the target service's requirements before choosing a route, then verify that its features work after connecting. If a service is unavailable, first distinguish connection issues from account eligibility instead of assuming every message indicates a route problem.
UNDERSTANDING THE PATH
IEPL, relayed and direct routes
Route types describe how traffic travels. The following sections explain common approaches and cost factors without treating technical labels as guarantees of performance. The same route type can perform differently across access networks and times of day.
IEPL
IEPL
How traffic is routed across borders
IEPL usually stands for International Ethernet Private Line. In network acceleration services, the term generally indicates that a dedicated line is part of the route, helping make resources and routing on that segment more predictable. It does not mean the entire path from your device to the destination website uses a dedicated line: your local connection, service entry point, exit and the website's response all affect performance.
These routes may be worth considering when session continuity, reliable file transfers or performance during work hours matter. Dedicated-line resources generally involve higher deployment and rental costs, but that does not translate directly into your actual speed or imply an extra charge in your plan. Check the Plans page and user panel for ShunVPN plan options and pricing, and test the connection on your own network before relying on it.
RELAY
Relayed routes
Connect through an entry point, then onward to an exit
A relayed route typically sends your connection to an intermediate entry point first, which then forwards it to an exit in the target location. This extra step allows more flexibility in routing and can sometimes improve performance compared with connecting directly from your local network to a distant exit. An extra hop is not always slower, just as fewer hops are not always faster; actual routing and network conditions along each segment are what matter.
Relayed routes can be considered for everyday browsing, access to tools in other regions and remote work. Their costs typically include the entry point, forwarding resources and exit, with the total depending on the configuration. Don't compare routes by name alone. Check whether pages and resources load fully, connections stay up and reconnects work smoothly. If a location offers multiple relayed entry points, compare them using the same task to avoid mistaking app cache differences for route performance.
DIRECT
Direct routes
Connect from your access network straight to the exit
A direct route generally means the client connects to the target exit through your local carrier's network, without an intermediate entry point configured by the service. “Direct” does not mean there are no routers along the way or that no client setup is needed. It describes the route in contrast to a relayed connection; the actual path across borders still depends on your access network and carrier routing.
When your local network has a suitable path to the target location, a direct route may be a simpler option. It typically avoids the cost of dedicated relay resources, but that does not mean it is always cheaper or right for everyone. Try it for browsing, downloading work files or comparing access to the target location. If performance is unsuitable at a particular time, compare relayed or dedicated-line options in the same location. Change the location and route type separately to identify what makes a difference.
CHOOSE BY TASK
Choose a route by use case
Start by defining what you need to do, then check whether the connection works for that task. Checking location, route type and app settings separately makes it easier to find a reliable option than switching at random.
Everyday browsing
If you don't need a specific location, start with a nearby location available in the user panel. Check that text, images, attachments and sign-in pages all load properly; seeing the homepage is not enough. Some sites serve text and images from different domains, so incomplete proxy rules can leave a page open but its resources missing.
If only one site has a problem, test other sites to check the connection, then review your client rules and browser settings. Once you find a suitable route, keep it as your everyday choice; you don't need to try every location just because more are listed. Site maintenance or account verification can also cause temporary access issues.
Streaming
First check the streaming platform's regional policies and account requirements, then choose an exit that meets them. Loading the homepage, signing in, browsing titles and playing a stream continuously are separate checks. Streaming availability depends on testing with the target platform; the locations listed here do not guarantee access to any specific platform or catalog.
If playback stalls, pause other network-intensive tasks and see whether the same program resumes. To compare routes, keep the program, video quality and local network consistent. After switching exits, an app may retain its old session. Stop playback normally and reopen the app before assessing the new connection.
AI tools
When using ChatGPT, Cursor or other AI tools, first check their supported regions and account requirements. A tool working in your browser does not mean your editor, command line or background processes use the same route. Test sign-in, request submission and response delivery separately, and make sure the app you use for work is configured as described by your client.
Long responses and code generation depend on sessions completing without interruption. Keep the same exit location during a task where possible, and avoid switching routes mid-request. If an error concerns usage limits, permissions or account status, follow the tool's guidance instead of repeatedly changing routes. For more on developer workflows, see our guide to Cursor acceleration and choosing a route for AI coding.
Gaming
Check the game's region, service rules and whether its client supports the connection method you need. A network acceleration subscription is not a service specifically optimized for any particular game, and cannot guarantee better in-game responsiveness. Make sure the launcher, account sign-in and game itself follow the same configuration; otherwise, only the updater may be using the proxy.
Don't switch exits during a match or an important session. If you need to compare routes, do so when it won't affect your progress, and distinguish game server maintenance, local Wi-Fi interference and client connection issues. If the app is incompatible with the current proxy method, consult its manual instead of repeatedly changing system network settings.
Remote work
For work, follow your organization's network and data-handling requirements first, then choose a route that meets the location requirements of your work. Check meetings, cloud documents, code repositories and file uploads separately; a problem with one does not necessarily mean the whole connection is unavailable. If an enterprise network client is also running, first check for conflicts between the two routing configurations.
For work that depends on a continuous session, check the connection before starting and keep the same exit during the task. ShunVPN supports unlimited concurrent devices, but devices sharing a local network can still affect the resources available to each other. After submitting important files, confirm they were saved remotely rather than relying only on the local progress indicator.
CHECK BEFORE CHANGING
Connection checks and routine maintenance
When something goes wrong, keep the current conditions and check one thing at a time. Changing only one factor at once helps identify whether the issue is your local network, route choice or target app.
From subscription to using your apps
Sign in to the user panel to check your subscription status, then update the route list as instructed by your client. Windows / macOS / iOS / Android / Linux are supported platforms. Download clients and retrieve subscriptions through the user panel; you must sign in to retrieve a subscription. Don't copy unverified configurations from public pages.
Select a route and, once connected, verify it in the app you actually plan to use. If websites work but a tool doesn't, check that tool's proxy settings first. If none of your destinations are accessible, check your local network and client status before trying another route in the same location.
Note the location, route type, local connection method and affected app; there's no need to share account details. Your subscription link provides access to your account, so don't post it in discussion forums or include it in public screenshots. If you need help, describe the issue in a support ticket through the panel, and hide your password and full subscription details.
Check the panel for route updates and refresh your subscription in the client as needed. Data resets monthly on your activation date. Data add-ons remain valid until used and never expire. If a connection fails, check your current data usage too, so you don't mistake a data issue for a location problem.