Route Guide · Location Index

International Routes and Server Locations

Choose a destination region first, then select a route type. This directory explains how locations and routes relate; check the app you plan to use to see whether a connection meets your needs.

Location directory

Browse routes by region

This static directory shows how to read locations, cities and route types; it is not a live list of options in your account. Check the user dashboard and client for currently available regions, cities and route types.

How to read the table: The country or region indicates the exit location, the city provides a more specific location, and the route type describes the connection path. These details do not certify platform compatibility. Streaming availability depends on the platform’s policies, your account region and the specific content.

On smaller screens, swipe the table horizontally to see all route types and streaming notes.

Static examples of international routes. Check each platform’s regional requirements for streaming availability.
Country or region City Route type Streaming availability
Asia-Pacific
JapanTokyoIEPLCheck the platform’s regional requirements
JapanOsakaRelayCheck the platform’s regional requirements
SingaporeSingaporeIEPLCheck the platform’s regional requirements
Hong Kong, ChinaHong KongRelayCheck the platform’s regional requirements
South KoreaSeoulDirectCheck the platform’s regional requirements
AustraliaSydneyRelayCheck the platform’s regional requirements
New ZealandAucklandDirectCheck the platform’s regional requirements
MalaysiaKuala LumpurRelayCheck the platform’s regional requirements
North America
United StatesLos AngelesIEPLCheck the platform’s regional requirements
United StatesSeattleRelayCheck the platform’s regional requirements
United StatesNew YorkDirectCheck the platform’s regional requirements
CanadaVancouverRelayCheck the platform’s regional requirements
CanadaTorontoDirectCheck the platform’s regional requirements
MexicoMexico CityRelayCheck the platform’s regional requirements
Europe
United KingdomLondonRelayCheck the platform’s regional requirements
GermanyFrankfurtIEPLCheck the platform’s regional requirements
FranceParisDirectCheck the platform’s regional requirements
NetherlandsAmsterdamRelayCheck the platform’s regional requirements
SwitzerlandZurichRelayCheck the platform’s regional requirements
SwedenStockholmDirectCheck the platform’s regional requirements
Other regions
BrazilSão PauloRelayCheck the platform’s regional requirements
ChileSantiagoDirectCheck the platform’s regional requirements
South AfricaJohannesburgRelayCheck the platform’s regional requirements
United Arab EmiratesDubaiRelayCheck the platform’s regional requirements

A location label is not the whole story

Choosing a Tokyo exit means requests may reach the target service from Japan. It does not change your account region, content rights or payment region. Some apps also check device location, account details, login history or other regional signals. Check the target service’s pages and prompts to decide whether a region is suitable; a route name in the client alone is not enough.

Different routes may be available in the same city. Even with the same city, the entry point, cross-border transit and exit network can differ. If you have connection issues, try another route type within the same region before switching regions. Changing one variable at a time makes it easier to tell whether the issue is with the route or the platform’s regional rules.

How routes work

IEPL, relay and direct routes: what’s the difference?

Route types describe how traffic reaches an exit, not how fast a connection is. Here’s what the terms generally mean and how their costs differ. Check the client labels and your own experience for the actual route.

IEPL

Focus on cross-border transit

IEPL generally refers to an international Ethernet private line, using dedicated cross-border transmission resources to connect networks at both ends. Other parts of the end-to-end route, including the connection from your device to the entry point and from the exit to the destination website, still affect performance. An IEPL label does not mean the entire connection uses dedicated resources or guarantee access to a particular website.

This type of route may be worth comparing for long sessions, sustained transfers or work. Focus on whether it can complete your tasks consistently, including at the times you typically use it. Dedicated transmission resources generally cost more to maintain and provision, but a higher cost does not make a route better for every app.

Relay

Connect to an exit through an entry point

A relay adds an intermediate point between your device and the destination exit. Traffic reaches the entry point first, then follows its assigned route to the exit. This changes how the route is organized; it does not simply add or reduce geographic distance. The entry network, subsequent transit resources and connection from the exit to the destination service all affect performance.

For everyday browsing, research and general app access, start by comparing relay routes. They typically require entry, forwarding and exit resources, with costs depending on the transmission method and capacity. A relay is not automatically a dedicated line, and its name alone does not tell you how stable it will be. Test it on your own network.

Direct

Connect directly from your device to the exit

A direct route generally means the client connects to an international exit without an additional relay entry point arranged by the service. “Direct” describes the service’s logical route; real internet traffic still passes through carriers and network exchanges. A simpler-looking route does not necessarily mean less physical distance or less congestion.

When your local network has a suitable path to the destination region, a direct route may work for general access and can serve as a comparison when troubleshooting a relay entry point. Its resource setup is often simpler, but actual costs also depend on exit resources. Direct routes are not inherently lower quality, nor are they the best choice for every network.

Route costs and plan prices are separate. These cost differences are technical context. They do not mean VPN37 charges separately by route type or indicate additional fees. See the plan pricing page and user dashboard for plan prices and data rules.

Why might switching route types make no difference?

A connection involves multiple steps. Your home Wi-Fi, background activity on your device, your carrier’s network, international transit and the target service can all affect performance. If the problem is between your device and local router, changing an international route may not help. If only one website is affected, check its account requirements and service status too. Route labels can help narrow down your options, but they can’t diagnose a fault.

Use cases

Choose a route for your needs

Check the service’s requirements first, then consider region and route. Change one setting at a time and see whether the task improves. This usually makes it easier to identify what works than switching through several regions at once.

Everyday browsing

Check that your usual websites load fully

Research, reading and web tools rarely require a specific city. If a site has no regional requirements, start by trying a nearby region and check whether login, images, attachments and in-page features all work. Distance is just a starting point; actual network traffic may not take the geographically shortest route.

If some content fails to load, first check the client’s mode and whether the relevant requests use the expected route. Then compare other route types in the same region. Keeping a reliable option for everyday browsing avoids repeated selection. Don’t change the exit region for every app just because one page loads slowly once in a while.

Streaming

Check content availability and account requirements first

Content on platforms such as Netflix, Disney+ and HBO depends on licensing regions, account plans and platform policies. Check which region offers the content you want, then choose a corresponding exit. Loading the homepage, seeing a title and playing it are separate checks; access to the homepage does not mean all content on the platform will play.

Streaming quality also depends on account permissions, device support, player settings and your local network. If playback stops, note the specific error and try another route in the same region rather than assuming it’s an account issue. Platform detection rules can change, so this page does not promise long-term support for any region. For more on how it works, see the complete guide to streaming access.

AI Tools

Consider session continuity and service regions

AI tools such as ChatGPT may involve more than loading a page: they can require ongoing generation, file uploads and authentication. Check the tool’s own regional requirements before choosing an exit region. Website access alone does not guarantee that your account, API or paid features will work; check account permissions separately.

Once you’ve confirmed the region is suitable, compare IEPL and relay routes across a complete task, such as whether generation finishes and uploads complete. With Cursor, Copilot or command-line tools, check that the app uses the network route configured in your client. Keep the exit consistent during work sessions where possible. For setup details, see our AI guide.

Gaming

Check the game region and client compatibility first

Game login, downloads and gameplay may use different services. Being able to open the game’s website in a browser does not mean the game itself uses the same route. Check the game region, the client’s network mode and platform rules before choosing a route. A regular international route is not the same as a dedicated gaming accelerator.

If the problem only occurs during a match, distinguish local Wi-Fi interference and game server issues from route problems. Compare route types within the same game region instead of switching straight to a distant one. This page does not guarantee compatibility or performance for any game. Follow the game publisher’s guidance if you’re unsure about protocols or usage restrictions.

Work

Keep a consistent exit to maintain work context

For document collaboration, code repositories, remote meetings and business apps, focus on whether you can complete tasks without interruption. Follow your organization’s rules for login regions, network access and data handling. Route selection does not replace corporate access authorization and should not conflict with network policies on work devices.

Once you’ve confirmed use is permitted, keep a suitable region and a backup route for your regular work. Save documents and finish active uploads before switching to avoid mistaking an interrupted session for a service outage. VPN37 supports Windows / macOS / iOS / Android / Linux, with unlimited simultaneous devices. Check the network mode and actual connection on each device.

Troubleshooting notes

What to check after connecting

Treat “connected” and “task completed” as separate checks. Specific prompts and details about what you were doing are more useful for troubleshooting than a general report that a route feels slow.

Check your subscription and route list

First check your subscription status in the user dashboard, then refresh the subscription in your client and make sure the selected route is still listed. If an example name on this page differs from the one in your client, follow the client’s list; there’s no need to look for an exact match. Import subscriptions and download clients through the user dashboard. Keep your subscription link private, and never include the full link in a public screenshot.

Check which route the app is actually using

After the client shows a successful connection, open a site you use regularly, then try the task in the target app. Browsers, desktop apps and command-line tools may use different network settings; one app not using the expected route does not mean the route itself is unavailable. If you use rule mode, check that requests to the target service are handled consistently, so login and content requests don’t take different routes.

Note the issue, then compare

When comparing routes, keep the device, local network, target service and task the same, and change only the route type within the same region. If the issue occurs in every region, compare using another local connection method. If only one platform is affected, first check its error message, account permissions and service status instead of assuming the region is the problem.

When asking for help, include the platform, route name shown in the client, time of the issue, target app and a redacted error message. Never share your password or full subscription link. Find troubleshooting advice in the Help Center. To report a specific issue, open a support ticket in the user dashboard.