Browse routes by region
The table below illustrates combinations of regions, cities and route types. It is not a list of currently available routes, and not every type is offered in every region. For full route names and current regional and route options, check the user panel after signing in and the client.
Streaming platforms determine access based on factors such as your exit location, account region and content licensing. We don't list guaranteed platform support. After connecting, check playback on the platform you want to use.
On narrow screens, swipe horizontally within the table. The country column also identifies the region.
| Country or Region | City | Route Type | Streaming Support |
|---|---|---|---|
| Asia-Pacific | |||
| Hong Kong, China | Hong Kong | Dedicated IEPL | Check after connecting |
| Singapore | Singapore | Dedicated IEPL | Check after connecting |
| Japan | Tokyo | Relay | Check after connecting |
| Japan | Osaka | Direct | Check after connecting |
| Australia | Sydney | Relay | Check after connecting |
| South Korea | Seoul | Direct | Check after connecting |
| North America | |||
| United States | Los Angeles | Relay | Check after connecting |
| United States | New York | Direct | Check after connecting |
| Canada | Toronto | Relay | Check after connecting |
| Canada | Vancouver | Direct | Check after connecting |
| Europe | |||
| United Kingdom | London | Relay | Check after connecting |
| Germany | Frankfurt | Dedicated IEPL | Check after connecting |
| France | Paris | Relay | Check after connecting |
| Netherlands | Amsterdam | Direct | Check after connecting |
| Switzerland | Zurich | Relay | Check after connecting |
| Sweden | Stockholm | Direct | Check after connecting |
| Other Regions | |||
| Brazil | São Paulo | Relay | Check after connecting |
| South Africa | Johannesburg | Relay | Check after connecting |
| United Arab Emirates | Dubai | Relay | Check after connecting |
| New Zealand | Auckland | Direct | Check after connecting |
Route Types and How They Differ
Dedicated IEPL, relay and direct describe connection paths, not fixed speed tiers. Understanding the path and testing it for your actual needs is more useful than relying on the route name alone.
Dedicated Network Link
IEPL typically refers to using an international Ethernet private line for the cross-border segment. The approach is to use a relatively defined network path for a key part of the connection rather than relying entirely on public-internet routing across borders. The connection from your client to the access point, and from the exit to the destination site, can still be affected by local network conditions.
This type of route may suit tasks where a sustained connection matters, such as remote collaboration, longer file transfers and conversations with AI tools. Dedicated capacity generally involves higher resource costs, but that does not imply an additional charge from VPNRich. Availability and use depend on the current plan and user-panel details.
When choosing a route, test whether it can handle your task continuously. A dedicated route does not guarantee access to a destination site, and it is not the same as a dedicated exit or a fixed performance guarantee.
Routed Through an Access Point
A relay route connects to an access point first, which then forwards traffic to the destination exit. By changing the connection and forwarding path, it may improve routing when your local network has trouble reaching a remote exit directly. An extra forwarding hop does not necessarily mean a worse experience; what matters is how well each part of the route works together.
Relay routes may suit everyday browsing, video streaming and general work, and can be an alternative to other routes in the same region. Resource costs depend on the access point, cross-border transport and exit configuration. The word “relay” alone does not indicate the cost, nor does a route name mean VPNRich charges separately for it.
If an access point performs poorly on your current network, try another relay route in the same region and check whether pages load and tasks complete more smoothly.
Direct Connection to a Remote Exit
A direct route typically connects the client to a remote server through the local network without using a separate relay access point provided by the service. “Direct” does not mean there are no intermediate devices in the physical connection; public-internet carrier networks and routing are still involved.
Direct routes may suit situations where international routing on your local network is smooth and your needs are relatively simple. They can also help you compare connection paths when troubleshooting. They avoid some resource costs associated with a separate relay hop, but the remote exit still has costs, so a direct route should not be assumed to be free.
Direct-route performance can change as carrier routing and usage times change. Don't stick with a route just because its name sounds simpler; judge it by whether it reliably handles the task in your target app.
Route Type Is Not a Plan Tier
Monthly plans: ¥9.9/month includes 60GB, ¥18/month includes 250GB, and ¥28/month includes 500GB. Data resets monthly on your activation date. Mid-cycle upgrades are prorated for the remaining days. For usage-based options, data packages never expire and can be used until depleted: ¥158/300GB, ¥358/1000GB and ¥658/3000GB. Don't infer plan benefits from route names. See the Plans page for details.
See Full Plan Details →Choose an Exit by Use Case
First check which region the destination service requires, then compare the available routes there. Change only the region or route type at a time. This makes it easier to identify the cause of an issue and keep connection settings that work.
Everyday Browsing
If you don't need a specific region, try a relatively nearby exit first, then check whether commonly used sites load completely. A page opening doesn't mean its images, sign-in components and file resources are all working; check those as part of your test. If a route in that region performs poorly, try another route type in the same region before switching to a more distant exit.
For everyday use, keep a primary and a backup route, and configure split tunneling for your actual browsing needs. Rules should match your client settings. If a site doesn't use the intended route, check whether the rule is being applied before repeatedly refreshing your subscription.
Streaming and Live Video
Start by identifying the region where the content is licensed, then choose the corresponding exit. Loading the platform homepage, finding a title and playing the full video are separate checks. Open the content you plan to watch and test playback, seeking and subtitle loading. Catalogs can also change based on your platform account, subscription benefits and licensing, so connecting through a particular country does not guarantee access to specific content.
Try to keep the exit unchanged during playback, especially for live streams and longer videos. If buffering occurs, lower the video quality first to see whether the connection stays stable, then compare a backup route in the same region. For more details, see Streaming Access and Route Selection.
AI Tools
Before using Claude, Cursor or other AI tools, check the service's regional and account requirements. An international route changes the connection path; it does not replace the provider's eligibility checks, account permissions or paid benefits. Once you've chosen a suitable region, try to keep the exit consistent, especially while generating a response or syncing code.
When testing, don't stop at the sign-in page. Try a real conversation, file submission or editor request. If the website works but the app doesn't, check whether the app uses the system proxy and review its own network settings. When handling work materials, follow your organization's data-handling policies.
Gaming Connections
Choose a route based on the region of the actual game server, not just the account region. Launcher downloads, account sign-in and multiplayer sessions may use different network paths, so check each separately. A general international route is not a dedicated gaming accelerator and does not guarantee compatibility with every game, platform or multiplayer mode.
Test before starting a live match, and check whether the game permits this type of connection. Changing exits during a match may interrupt the session; if your current setup is stable, leave it as is. If you're unsure whether a game supports this connection method, check the publisher's rules before using a proxy connection.
Work and Collaboration
For work, prioritize session continuity. Email, document collaboration, meetings and remote systems may all be in use at once, so check that your regular tasks can continue without interruption. If your work systems restrict access by exit location, check your organization's requirements before changing regions. Don't try to resolve access-permission issues by repeatedly switching routes.
VPNRich supports Windows / macOS / iOS / Android / Linux, with unlimited simultaneous devices. Each device still needs its own client setup. Running a company connection alongside this service may cause routing conflicts; configure split tunneling according to your work environment. No-logs practices do not replace the privacy and compliance rules of your work platforms.
Post-connection Checks
Even after choosing the right region, make sure your subscription, client and app settings are consistent. When troubleshooting, keep track of what you've already tested and avoid changing several settings at once, so you can identify the source of the issue.
Check Your Subscription, Then Your Exit
Open the user panel to check your subscription status and remaining data, then update the subscription list in your client. An older list may still contain route names or paths that have changed, so using a saved route does not always show what's currently available. The client and subscription links are in the user panel; you don't need to look elsewhere for an installer or subscription URL.
After connecting, use My IP to check your current exit information, then test the target app with a real task. An expected exit location only confirms that the connection path has changed; it doesn't replace checking streaming playback, an AI conversation or work-system sign-in.
Tell Route Issues from App Issues
If no websites load, disconnect first, check that your local network is working, then reconnect in the client. If only one app has an issue, check whether it's using the intended proxy, whether it has regional requirements and whether your account has the necessary permissions. If the same message appears after switching routes in the same region, the connection path may not be the only cause.
For help, submit a ticket through the user panel and include your device platform, route name, target app and a description of the error. Don't share your password, full subscription URL or other sensitive credentials. You can attach a screenshot with sensitive details hidden to help identify whether the issue involves your subscription, connection or app.