REGION INDEX
Browse routes by location
The table below highlights popular locations; it is not a complete server list. Check the dashboard for current cities, route names, and types. Location coverage does not mean every route type is available in every location.
| Country / region | City | Route type | Streaming availability |
|---|---|---|---|
| Asia-Pacific | |||
| Japan | Check the dashboard | See dashboard details | Check with the platform |
| Singapore | Check the dashboard | See dashboard details | Check with the platform |
| Hong Kong | Check the dashboard | See dashboard details | Check with the platform |
| North America | |||
| United States | Check the dashboard | See dashboard details | Check with the platform |
| Europe | |||
| Italy | Check the dashboard | See dashboard details | Check with the platform |
| Other locations | |||
| Find other countries and cities in the dashboard's route list. This page does not list unverified servers. | |||
On narrow screens, swipe horizontally within the table. Hong Kong is listed by route exit location; the header uses the country field. This table does not show speed tests, load, or live status.
A location label doesn't show the full route
In a client, a location label usually identifies the exit location; it does not mean requests travel only through that region. The entry point receives the connection, the route carries traffic to the exit, and the destination website handles the request based on the exit IP and its own policies. Consider the exit location and route type separately—names alone cannot tell you how well a connection will perform.
The streaming column is not a fixed compatibility list. Detection can vary between exits in the same location, while account region, content rights, and platform policies can also affect the available catalog. To watch specific content, connect and check directly on the platform. A country label is not a guarantee that content will be available.
PATH REFERENCE
IEPL, relayed, and direct routes
These terms describe how traffic is routed, not a ranking of performance. The sections below outline common setups; check the dashboard for details about each route.
IEPL
IEPL generally refers to an international Ethernet private line. It provides a dedicated transport connection between designated endpoints, with a different cross-border transport setup from standard public-internet routing. For users, what matters is how this part of the route connects the local entry point to the destination exit—not the label alone. An IEPL route does not guarantee identical performance for every connection.
These resources typically involve costs for ports, transport capacity, and access maintenance, with a cost structure different from a direct public-internet connection. But a dedicated line is only one part of the full connection: the local network, entry point, and route from the exit to the destination can all affect performance. It does not replace eligibility requirements set by a destination service or guarantee that an app will have no restrictions.
A dedicated line may suit tasks where a consistent connection matters, such as remote work, longer AI conversations, or extended video streaming. Compare routes under similar local network conditions by checking whether the task completes and whether interruptions recur. Treat the route name as a description, not a test result. Route types do not have separate prices on this page; see the plans page for current plan details.
Relayed routes
A relayed route sends requests to an intermediate access point first, which then forwards them to the exit. The relay changes how traffic is connected and forwarded, so the route from your local network to the exit does not rely solely on a direct connection. It adds a forwarding step, but the number of steps alone does not determine performance.
Relayed routes typically use a combination of access nodes, forwarding resources, and exit resources. The actual costs depend on the networks and capacity involved. A relay is not simply a cheaper version of a dedicated line, and the route name does not reveal plan costs. For everyday browsing and mixed app use, the key questions are whether the entry point suits your local network and whether connections to your destinations remain stable.
If a route connects but often stalls while loading content, keep the destination location the same and compare it with a route using a different path type. This isolates the transport route instead of changing the location, app, and network all at once. Test the specific task to see whether a relay works for you.
Direct connections
A direct connection usually means the client connects straight to an exit server, without an additional relay entry point on the service side. Direct describes how the connection is set up; it does not mean the physical distance is shortest or that traffic avoids carrier routing. Requests still travel through your local access network and the public internet to reach the destination server.
This route avoids an intermediate forwarding step on the service side, making its resource setup more straightforward. In practice, performance depends more on your local carrier, the public-internet route across borders, and the destination exit. Cost differences do not determine quality: one direct route may work well on your network while another may perform differently at the same time. There is no single verdict for the entire route type.
Direct routes are a useful starting point for testing everyday websites, research, and app sign-ins. If an exit works for you, keep it as a regular option. If the connection is unstable, compare other routes instead of repeatedly refreshing the page. Route types are clues for troubleshooting, not a ranking you need to memorize.
WORKLOAD MATCH
Choose a route for your needs
First check which location an app requires, then verify that you can complete the task. Network distance is only one factor; the destination service's regional policies and your client’s routing settings matter too.
Everyday browsing: check that the whole page loads
For research, reading websites, and everyday app access, start with a commonly used location that suits the destination service. Don't just check whether the page title appears—make sure images, sign-in components, and embedded resources load too. Some sites fetch content from multiple domains. If the main page opens but some resources are missing, check whether your client rules cover those requests.
Once you find a route that works, keep it as your everyday option. There's no need to switch just because more locations are available. If one site won't open, check whether the issue is limited to that site, then try another route in the same location. A fully working page is a better guide to your regular choice than the number of locations listed.
Streaming: check regional access and playback separately
For streaming, first check whether the content is available in your chosen region, then whether the platform accepts your account and exit. Access to a platform's home page does not mean your account can play every title, and catalogs can change with licensing arrangements. After connecting, open the title you want, confirm it plays, and check for interruptions during playback.
If only a specific title is unavailable, check its regional availability and any account messages first. If several videos struggle to load, compare another route. After changing exits, an app may retain an old session or region setting; reopen the page using the app's normal steps. Changing routes does not change your account entitlements.
AI tools: keep a consistent exit and test the full task
Tools such as ChatGPT, Claude, Gemini, and Cursor may consider your exit region, account details, and request patterns. Check the service's current availability first, then keep a suitable exit consistent where possible instead of repeatedly changing networks during sign-in and use. Network acceleration does not replace the service's own account eligibility requirements.
Don't stop at a successful sign-in. Check that tasks such as generating responses, handling files, or making requests in an IDE work as expected. Web apps and developer tools may use different proxy settings; if a browser works but an extension doesn't, check the extension configuration first. See the AI Tools guide for configuration details.
Gaming: match the server region and client route
First check the region of the server you actually connect to, rather than choosing a route based only on the launcher's store region. Sign-in, updates, and gameplay may use different connections. A launcher opening successfully does not mean game traffic is using the selected route. Check the client's routing rules and any information shown by the game.
Once you've chosen an exit for the target server, check connection stability in the game itself. Avoid switching exits repeatedly during a match to prevent interrupting the session. R1VPN is a cross-border network acceleration subscription service; this page does not make game-specific performance claims for general-purpose routes.
Work: keep sessions stable and separate work from local resources
Video meetings, remote collaboration, and business systems often rely on persistent sessions. Before choosing a route, check whether your work systems have requirements for exit region, connection method, or device environment. Follow your organization's policies for corporate access rather than relying only on whether a webpage opens. Keep the network path consistent during meetings and file transfers where possible.
When accessing local printers, intranet resources, or dedicated business clients, also check that your routing setup is appropriate. R1VPN supports Windows / macOS / iOS / Android / Linux, with unlimited devices, but proxy settings still need to be checked on each device. Using multiple devices at once does not mean they automatically use identical routes.
CONNECTION CHECK
Connection results and troubleshooting
Compare the same task to pinpoint where the problem occurs before switching routes. This helps avoid unnecessary changes and makes it easier to explain the issue in a support ticket.
Before connecting
First make sure your local network can access everyday services, then check that your subscription status and client configuration are up to date in the dashboard. The client and subscription links are available in the user dashboard. Follow the Guides to import your subscription, then choose a location and route shown in the dashboard.
After connecting
Open My IP to check your exit details, then complete a real task in the target app. An IP lookup is only a helpful check, and websites may use different geolocation databases. If the lookup location differs from what the app reports, judge by the destination service's actual behavior.
If something goes wrong
Note your local network type, device platform, selected route name, destination service, and any error message. If another route in the same location completes the same task, record that comparison too. Don't include account passwords or full subscription links in public screenshots.
Need more help?
Start with the connection guidance on the Support page. If the issue persists, submit what happened and your comparison results through a dashboard support ticket. It's easier to troubleshoot when you specify whether the failure occurred during connection, sign-in, loading, or continued use rather than simply saying it doesn't work.
Check coverage and plans separately
Location coverage helps you choose an exit; plan traffic limits determine how much you can use. They are separate measures. Monthly subscription traffic resets each month on the activation date. If you upgrade mid-cycle, the price difference is prorated for the remaining days. Data add-ons remain available until used and never expire. See plan pricing for prices and billing details.
R1VPN keeps no logs and offers a 60-day money-back guarantee. You can create an account with a username and password—no email address required. Learn about route selection and client setup, then choose a plan that fits how you use the service.