VPNXiaoXiao / Regional Directory

Global Server Locations

Find an exit city by country or region, then compare route types by use case. The table below lists sample routes; available options may vary by client.

Countries covered
110+ countries
Routes covered
150+ routes

Regional Route List

Cities indicate where each route exits. “Not listed” means streaming support information has not been published; it does not indicate whether a service is supported. Scroll horizontally on smaller screens to view the full table.

Country or regionCityRoute typeStreaming support
Asia-Pacific
Hong Kong, ChinaHong KongIEPLNot listed
JapanTokyoRelayNot listed
SingaporeSingaporeDirectNot listed
North America
United StatesLos AngelesRelayNot listed
Europe
United KingdomLondonDirectNot listed
ItalyMilanRelayNot listed
Other
Sample routes for other regions are not listed on this page. Check the client for available options.

Want to check your current exit location? Open My IP to view the results. IP geolocation can provide an initial check, but each website determines your location according to its own criteria.

Route Types and Costs

An exit city shows where traffic leaves the service network; a route type describes how data reaches that exit. The connection path can vary even when the exit city is the same. These are network configurations, not plan tiers, and a route label alone does not determine speed or cost.

Dedicated connections

IEPL

IEPL is an international Ethernet private line. Part of the transmission between service networks uses a designated Ethernet circuit instead of relying entirely on the public internet to select routes at each hop. The private line describes only one segment between service networks; the path from your device to the access point and from the exit to the destination website depends on other network conditions. Congestion on your home Wi-Fi or a slow response from the destination service can also affect the experience.

Private lines typically involve circuit leasing, access, and maintenance, so their fixed costs are often higher than using the public network directly. If you regularly spend long periods in meetings or working remotely, compare whether brief interruptions or reconnections occur during your working hours. Try real tasks on the same device before deciding whether this route suits you. A private-line label does not mean it will always be faster in every situation.

Forwarded through an access point

Relay connection

A relay connection first sends traffic to the service provider’s access point, which then forwards it to the selected exit. The access point and exit can be in different regions: the former affects how your local network enters the service network, while the latter affects the location websites see as the source of your connection. An extra access point does not necessarily mean a slower connection; if it avoids a congested segment on the direct route, performance may be steadier.

Relay connections require the provider to maintain access nodes and forwarding links. Costs depend on data center facilities, carrier interconnections, and forwarding resources. They also add another point to investigate when troubleshooting. If a direct connection to the same exit often stalls at predictable times, try a relay on the same network and at a similar time, then compare web loading, file transfers, or voice calls.

Direct access to the exit

Direct connection

Direct means the client connects to the exit node without using an additional relay access point set up by the service provider. It does not mean traffic travels through the physical network without passing through routers. The actual path still depends on carrier routing and interconnection. Users in the same city on different carriers may see different connectivity even when they choose the same exit.

Direct connections skip the provider’s relay infrastructure, which generally makes the network setup simpler, but quality data centers and interconnection resources still cost money. For everyday research or web browsing, start with a direct connection to a suitable region as a baseline. If pages load quickly at first but stall during continued use, compare other route types with the same task rather than choosing based only on how quickly the homepage opens.

Choose a route by use case

First check the destination service’s regional requirements, then compare routes using tasks you perform regularly. Keep the device, local network, and time of day consistent during testing, and change only the route each time. Otherwise, it is difficult to tell whether the difference came from the exit or a change in your local network.

Everyday browsing: Check for consistent loading

Start with an exit that is convenient from your local network and suits your access needs. Open frequently used sites in succession and check whether images, attachments, and subsequent pages load properly—not just the homepage. If only one site repeatedly fails, check whether that site is working before switching to another route in the same region. If several sites slow down at once, check your local Wi-Fi signal and background downloads too.

Streaming: Check the catalog separately from playback

First check the platform’s permitted regions, account entitlements, and the title you want to watch. Then play a full segment and see whether playback resumes after seeking. Opening the platform homepage does not guarantee that your account can play a particular title, and starting playback does not mean high quality will be sustained. If you see a region restriction, check your account and exit location; if playback buffers, focus on sustained playback performance.

See the streaming route guide →

AI tools: Test the full workflow from one exit

Check the tool’s regional rules first, then choose an eligible exit. Use the same route to sign in, submit a request, wait for a long response, and upload any required files. Note where interruptions occur. If you encounter an additional verification step during sign-in, avoid repeatedly switching regions to retry; check your account status and the tool’s announcements first. Response times also depend on server-side processing, so they are not a reliable measure of route quality by themselves.

Gaming: Match the game region and client

Check the game region first, and confirm that your client and connection mode are compatible with the game’s traffic. Test in training or another non-ranked mode, and watch for inconsistent input response or choppy voice chat. An exit close to the player does not necessarily mean a short route to the game server. If brief stalls are common during matches, compare other routes for the same game region rather than switching regions blindly.

Work: Test calls and uploads

Choose an exit in line with your organization’s network and device policies. Before a meeting, test voice, screen sharing, and uploading a typical work file to confirm that the relevant apps work properly. Avoid changing exits during an important meeting or transfer, as this may trigger another app verification or interrupt the task. If your usual route has problems, switch to a tested backup and check whether the meeting client or cloud drive can resume.

If the issue only occurs in the evening, test again at the same time. If the same service is still the only one affected after changing routes and local networks, check its status and any account notices first. For more on routing and congestion, see the protocol reference.