NETWORK / REGIONS

Serverlocations and route selection

VPNUL covers 110+ countries and 220+ routes. Start with the region where your target service is based, then compare route types and real-world connection performance.

Start Free ▸ View Plans

Create an account with a username and password—no email address required. Check the user panel for current route availability and supported services.

REGION DIRECTORY

Browse route examples byregion

This table shows how regions, cities and route types are listed; it is not a complete route list. Routes may change during maintenance or network adjustments. Sign in to see currently available routes, their names and supported services.

Please note

The “Streaming support” column does not guarantee access. Streaming platforms can change how they identify locations, and routes in the same region may perform differently. Check the route details and test it in the app you want to use.

Country or regionCityRoute typeStreaming support
Asia-Pacific
SingaporeSingaporeRelayedCheck route details
JapanTokyoIEPLCheck route details
JapanOsakaRelayedCheck route details
South KoreaSeoulDirectCheck route details
Hong KongHong KongRelayedCheck route details
AustraliaSydneyDirectCheck route details
North America
United StatesLos AngelesIEPLCheck route details
United StatesSan JoseRelayedCheck route details
United StatesNew YorkDirectCheck route details
CanadaVancouverRelayedCheck route details
CanadaTorontoDirectCheck route details
MexicoMexico CityDirectCheck route details
Europe
United KingdomLondonRelayedCheck route details
GermanyFrankfurtIEPLCheck route details
FranceParisRelayedCheck route details
ItalyMilanDirectCheck route details
NetherlandsAmsterdamRelayedCheck route details
SpainMadridDirectCheck route details
Other regions
United Arab EmiratesDubaiRelayedCheck route details
TurkeyIstanbulDirectCheck route details
South AfricaJohannesburgDirectCheck route details
BrazilSão PauloRelayedCheck route details
ChileSantiagoDirectCheck route details
IndiaMumbaiDirectCheck route details

A city name indicates the region a route exits through; it does not mean the entire connection from your location to that city follows one physical path. Cross-border traffic also passes through your local access network, carrier interconnections and the target service’s own network. Distance to a city alone cannot predict the experience end to end.

Different cities or route types within the same country are listed to help you compare options for different needs. If a service requires a specific region, choose that region first, then test the available routes. If it has no regional requirement, prioritize stability when loading the target page; you do not need to stick with the first route in the table.

ROUTE TYPES

Dedicated, relay and direct routes

Route types describe how a connection is routed, not the result of a single speed test. The destination region, your local network and the time of day all affect performance.

IEPL / PRIVATE PATH

IEPL

IEPL generally refers to a cross-border connection carried over dedicated network capacity. Traffic first reaches an access point, travels over the dedicated link to the other end, then continues to the target service through an egress route. Compared with paths relying entirely on regular public internet peering, the middle section is easier to plan. The access point, egress point and target service can still affect the overall experience.

Consider testing a dedicated route if you regularly use cross-border work systems, need long collaboration sessions, or often experience route fluctuations in a region you use. It may suit use cases where connection stability matters most; the route name alone does not mean every app will be faster.

Dedicated network capacity generally costs more to build and maintain, so weigh it against your actual needs. For brief web browsing, first test whether a regular route is sufficient; a dedicated route does not have to be your only option.

RELAY / TRANSIT

Relayed routes

A relayed route sends your connection to an intermediate access point before forwarding it to an egress point in the target region. The intermediate point can reorganize the onward path: when direct peering between your local network and a distant egress performs poorly, a suitable relay may provide a steadier connection. A relay adds another part of the path to consider, so “relayed” does not mean “always faster.”

For everyday browsing, cross-border document collaboration and region-specific content, start by testing a relayed route in the target region. Check whether pages load consistently, long-lived connections stay active, and the expected egress is still used after navigating. If performance is unstable, compare other route types in the same region.

Relayed routes require access and forwarding resources. Their costs are generally between those of simple direct routes and dedicated network capacity, but the exact setup varies by route. Test the target app rather than inferring cost or speed from the route type.

DIRECT / PUBLIC PATH

Direct routes

A direct route generally means no dedicated carrier or intermediate forwarding point is specifically arranged; the connection relies mainly on regular network peering to reach an egress in the target region. Its routing is relatively straightforward, making it a useful baseline for everyday access. Carriers and peering points along the way can still vary, so “direct” does not mean there are no intermediate network devices.

Start with a direct route to read international websites, access services without strict regional requirements, or check whether an app works at all. If pages load smoothly and sessions remain stable, there is no need to switch just to try a different route type. If performance fluctuates at certain times, try a relayed or dedicated route in the same region.

Direct routes generally require fewer additional forwarding resources, but route costs depend on more than the route label; egress and peering arrangements matter too. You do not need to guess quality from a cost label. Keeping a tested backup route can be more useful when occasional connection issues arise.

SELECTION NOTES

Choose aroute for your needs, then test it with the service

First check whether the egress region suits your use case, then compare routes. The steps below are for troubleshooting, not a performance guarantee for any region or route.

Everyday browsing

For research, email and regular websites, start with a nearby region where the sites you need are accessible. Open your usual sites, browse several pages in a row, then check that images and attachments load fully. A direct route is a good starting point; if some pages load inconsistently, keep the same region and compare a relayed route. Avoid changing browser settings, egress region and route type at the same time, or it will be hard to identify what made a difference.

Streaming and video

First check which region offers the content you want, then review the supported-services information for that region’s routes in the user panel. After connecting, check the catalog and playback on the target platform—not just whether its home page opens. Regional detection, account details and content licensing can all affect access; the route’s city alone cannot determine whether a particular title will play. If playback fails, close and reopen the app, then try another listed route in the same region.

AI tools

AI tool websites, sign-in flows and long sessions may use different request paths. After choosing a region that meets the service’s access requirements, test more than the home page: check sign-in, submit a request and keep the connection active while content is generated. If the site opens but requests fail, check your account status and the service’s own messages, then compare other routes in the same region. Regional rules vary between tools and can change, so check the target service’s current requirements.

Gaming

First check the game server’s region, then choose a matching egress and test sign-in and an actual match. Smooth web browsing does not guarantee responsive in-game interactions: the game’s protocol, server load and your local access network can all play a part. Focus on consistent controls and a stable session. If only one game has issues, check its regional and network requirements. Switching egress regions frequently may also trigger the game’s account security checks.

Cross-border work

Choose a route based on the region of your team’s collaboration platform, document system or meeting service. Opening the website is only the first step; also check whether file uploads, real-time collaboration and calls remain connected. For long work sessions, compare dedicated and relayed routes and note which works well with your regular services. If your company system requires a fixed egress or has other network access rules, follow your system administrator’s instructions first.

ROUTE PRACTICE

Turnserver names into practical choices

Route names often include a region, city and type. The region tells you where the service will see the egress; the type describes roughly how the connection reaches it. Neither one alone determines the result. For content restricted to a specific region, matching the egress matters more than choosing a nearby city. For sites with no regional restrictions, compare how consistently common routes work on your network.

When saving a frequently used route, note the target service and region rather than just a city name. If a platform changes its rules, local network conditions shift or a route is maintained, you may need to test your choice again. The user panel has current route information; this public table is a guide, not a substitute for the live list.

VPNUL supports Windows, macOS, iOS, Android and Linux. Update your subscription in the client before checking the route list to avoid missing a region because you are using an old list. Find subscription links and client downloads in the user panel; do not share personal subscription links as a public route directory.

Keep plan usage in mind when choosing routes. Monthly plans include ¥9.9/month with 60GB, ¥18/month with 250GB and ¥28/month with 500GB. Data resets monthly on the activation date. Pay-as-you-go data bundles do not expire. See the plan details to choose based on your usage; the number of routes does not indicate how much data you will use.

If connection issues recur across multiple regions, note the platform, route name shown in the client, affected service and error message. This is more useful for troubleshooting than simply saying a region is slow. For account or subscription issues, sign in to the user panel and submit a support ticket. VPNUL offers a 60-day no-questions-asked refund policy. See the Terms of Service for details.

Start Free