Choose an exit location first, then compare route types. Streaming, AI tools, and work have different requirements; one route does not need to cover every use case.
90+ countries
240+ routes
Unlimited devices online at once
No logs
This page provides a static location index and guidance for comparing routes, not a complete list of available servers. Check the client after signing in for specific cities, server names, route types, and current availability.
Location / Exit Point
Browse routes by location
Here are some of the publicly listed locations. Overall coverage does not mean every location offers the same route types, or that every route works with every streaming platform.
Popular Locations · Check the Client for the Full List
Country / Region
City
Route Type
Streaming Support
Asia-Pacific
Singapore
Check the client
Refer to the labels shown in the client
Verify against the platform's regional and account requirements
Japan
Check the client
Refer to the labels shown in the client
Verify against the platform's regional and account requirements
Hong Kong
Check the client
Refer to the labels shown in the client
Verify against the platform's regional and account requirements
North America
United States
Check the client
Refer to the labels shown in the client
Verify against the platform's regional and account requirements
Europe
Italy
Check the client
Refer to the labels shown in the client
Verify against the platform's regional and account requirements
Other
For other locations, cities, and route types, check the full list in the client. This page does not add unverified entries.
City and route type entries in this table include verification notes to avoid presenting a location as a specific data center or fixed product configuration. Before choosing, check the full name currently shown in the client. If you need content from a particular region, also review the target platform's service requirements for that region. Don't assume a route is suitable based only on its flag or proximity to another location.
Network Topology / Routing
Dedicated, Relay, and Direct Routes
Route types describe how data travels across the network. Protocols describe how a client establishes a connection. They are different things.
IEPL Dedicated Routes
IEPL generally refers to a transmission path using dedicated Ethernet links. It separates some parts of the route from ordinary public internet routing, with an emphasis on controllable links. The actual entry point, exit point, and access method depend on the route configuration; the name alone does not mean the entire path uses the same resources.
These routes can suit tasks that depend on a steady connection, such as extended streaming, video calls, and ongoing file transfers. Dedicated links typically involve higher resource costs, but that does not make them the best choice on every network. Home internet quality, wireless interference, and the destination service can all affect the experience.
Relay Routes
A relay route sends your connection to an intermediate access point before forwarding it to the exit location. The extra hop is intended to provide a better link between networks, not simply to minimize the number of locations along the way. Connection quality between your network and the entry point matters just as much as the exit location.
Relay routes can work well for everyday browsing, work, and comparing different access paths. Their resource costs depend on how the entry point and onward links are set up; the label alone does not indicate price or performance. If your connection fluctuates, try another entry point in the same exit location to see whether the issue is the location or the specific route.
Direct Routes
A direct route generally means the client connects to the route's entry point without an additional relay access point configured by the service. “Direct” describes how the service organizes the route; it does not mean there are no routers on the internet or that the physical distance is shorter.
Direct routes have a relatively simple structure. They can suit networks with good routing between your local connection and the entry point, and can make basic connectivity easier to assess. They tend to depend more on changes in public internet routing. Their resource costs differ from those of dedicated routes, but that does not reveal the fixed cost of any particular route in a plan. Choose based on how the route performs for your actual task, not on an assumption that “direct” always means faster.
What Route Labels Can and Can't Tell You
Route types can help explain differences in network paths, but they don't tell the whole story. Slowdowns in the evening may come from congestion on your local network, routing between carriers, competition for exit resources, or the destination website itself. Compare different route types in the same location under similar conditions. Check for differences in page loading, uninterrupted playback, and session stability before choosing a regular route.
Protocol names such as Trojan, VLESS, and Hysteria2 should not be confused with locations or route types. Check the actual list to confirm whether the client supports a protocol and how a route is configured. For more on connections, transmission methods, and resource use, see the Protocol and Routing Technical Guide.
Use Cases / How to Choose
Choose a route for your use case
Start with the task you need to complete, then choose a location and route type. There's no need to keep switching without a clear goal.
Everyday Browsing
Start with a location that falls within the target website's service area. Then check that pages load fully, images display correctly, and your sign-in stays active. A nearby location can be a useful starting point, but network traffic doesn't always take the shortest geographic path. If the homepage loads but a content page fails, check the site's account and access requirements before changing all your connection settings.
For everyday browsing, keep a regularly used route as a baseline. If something goes wrong, compare the same page on another route. Don't change the location, protocol, and client mode all at once; even if the issue goes away, you won't know which change helped.
Streaming and Netflix
For streaming, check the content's region and your account requirements first, then assess playback stability. A platform homepage loading doesn't guarantee a particular title will be available; seeing a title doesn't guarantee the current network can sustain playback. After connecting, test the actual playback page: start a video, seek, and watch for a while instead of relying only on the client's connection indicator.
If you see a regional restriction, check the detected exit location and your account region first. If playback works but keeps buffering, compare other route types in the same location. An IEPL dedicated route may be worth trying for sustained streaming, but this page makes no blanket guarantees about any specific platform, content library, or video quality. Keeping the location the same also makes it easier to distinguish platform requirements from routing issues.
AI Tools
When using AI tools, distinguish between accessing the website, signing in, and completing a task. An input box appearing means only that the page has loaded. Whether a request succeeds can also depend on the platform's service regions, account permissions, task limits, and current service status. Verify access by entering a prompt, submitting it, and checking the result.
Long responses, file uploads, and ongoing sessions rely more on a stable connection. Avoid switching routes mid-task when one is already working. If the site loads but a task fails, check the platform's message first, then compare other routes in the same location. A network plan does not include membership, credits, or account eligibility for third-party AI platforms.
Gaming Connections
For gaming, check the actual region of the game server rather than relying only on the store region. Downloads, sign-ins, and gameplay may use different services, so success at one stage doesn't guarantee the others will work the same way. Confirm that the client configuration supports the required connection method and meets the game's requirements.
When choosing a route, watch for dropped connections, noticeable lag spikes, and interruptions to voice chat. An international route plan is not a substitute for game-specific compatibility guidance; this page does not guarantee access to any particular game. Avoid switching routes mid-match. Compare them during testing or other non-critical activity.
Work and Video Calls
Work tasks often depend more on a stable connection than on loading a webpage once. Test video calls, shared document syncing, and file transfers separately, since each uses the connection differently. Before an important meeting, use your planned route to check your microphone, video, screen sharing, and document access. Once confirmed, keep the exit location unchanged where possible.
Work systems may have their own requirements for sign-in location, device permissions, or internal networks. Don't assume changing your network will solve every account issue. If your organization provides a connection tool, follow its usage policies. Running multiple network tools at once may also cause routing conflicts.
Verification / Troubleshooting
Connection Checks, Step by Step
Check Your Local Network First
Before comparing routes, check that your local network is working properly. An unstable Wi-Fi signal, ongoing transfers on other devices, or changes to system network settings can cause similar issues across different routes. If all target websites are affected, restore your basic connection first, then compare routes to avoid unnecessary switching.
Then Check the Exit Location and Route
Once the client shows a successful connection, use IP Lookup to check the exit information seen by your browser. Other apps may use different routes, so this only describes the path used by the current request; it doesn't verify every app. In split-tunneling mode, also confirm that the target app is using the selected route.
Finally, Complete the Task
Try a real task in the target app: open a content page, start playback, send an AI request, or join a meeting. Only completing the task can tell you whether the route suits it. If you need to report an issue, note the route name, platform, error message, and steps to reproduce it. Don't share subscription links or account credentials publicly.
Plans / Usage Limits
Route Selection and Plan Usage
Choose a Plan Based on Your Usage
Monthly plans: ¥9.9/month for 60GB, ¥18/month for 250GB, and ¥28/month for 500GB. Data resets monthly on the activation date. Mid-cycle upgrades are prorated based on the remaining days. Data packs: ¥158 for 300GB, ¥358 for 1000GB, and ¥658 for 3000GB. They last until used and never expire.
Streaming, file transfers, and everyday browsing use data differently, so the best billing option varies. Check your actual usage in the dashboard before changing plans. Don't assume a route name means a plan includes extra benefits; check the dashboard for available routes and plan details.
VPNWB supports Windows / macOS / iOS / Android / Linux, with unlimited devices online at once. Client features, split-tunneling settings, and network conditions can vary by device, so check performance separately on each device, even when using the same location.
No email address needed; create an account with a username and password. Get the client and subscription through the user dashboard. Sign in to access your subscription; the iOS client entry point also requires an active plan. Pay with Alipay / WeChat Pay / USDT. A 7-day refund policy is available.