Choose a region · Route list

Global VPN Servers

First identify the exit region required by the service you want to access, then compare direct, relay and IEPL routes. Route type describes how traffic travels; it doesn’t mean one route is best for every use.

Browse by region

VPN Server Route Overview

Start by choosing the country or region for your exit location. Cities distinguish routes within a region; if a city isn’t listed here, check the client. Streaming availability isn’t inferred from a route’s region or type.

On narrow screens, swipe horizontally to see the streaming labels at the far right of the table.

Country or regionCityRoute typeStreaming support
Asia-Pacific
SingaporeSingaporeDirectCheck the label in the client
Hong KongHong KongIEPL Dedicated LineCheck the label in the client
JapanCheck the clientRelayCheck the label in the client
North America
United StatesCheck the clientCheck the clientCheck the label in the client
CanadaCheck the clientCheck the clientCheck the label in the client
Europe
ItalyCheck the clientCheck the clientCheck the label in the client
Other regions
Other locations aren’t listed individually on this page. Check the client.

A region name refers to the route’s exit location, which may differ from the first point your client connects to. To check whether streaming works, verify the route label, the platform’s regional catalog and your account access separately.

Route design and cost

IEPL Dedicated Lines, Relays and Direct Connections

Route type and connection protocol aren’t the same thing: route type describes the network path traffic takes, while a protocol defines how the client and server establish a connection. When troubleshooting, change one setting at a time so you can identify what made the difference.

An IEPL dedicated line uses leased capacity for the cross-border segment of a route instead of relying entirely on standard public internet routing for that segment. Other sections, such as the connection from your device to the access point and from the exit to the destination, are still affected by your local network and the destination service. During evening peak hours, if pages load but long sessions keep dropping, keep the exit region the same and compare the dedicated line with other routes while repeating the same task.

Dedicated lines typically involve leased capacity and maintenance costs. Here, cost refers to differences in building and operating routes, not a separate charge. Don’t choose based on the label alone: for video calls, consider whether audio stays connected in both directions; for remote desktops, notice whether controls suddenly lag. These are more useful indicators than the first impression at connection time.

A relay route first sends traffic to an access node, which then forwards it to the selected exit. If the public internet path from your local network to the exit isn’t ideal, connecting through a relay node that’s easier to reach may sometimes be more stable than going directly to the same exit. On the other hand, a congested entry point or a longer path after forwarding can make responses slower.

Relays require additional access and forwarding resources; costs depend on the entry point, exit and how they’re connected. Treat a relay as an alternative in the same region: if a direct route often requires retries, switch to a relay in that region and repeat the same task. Keep the destination and protocol unchanged to help tell whether the difference comes from the exit region or an improved path along the way.

With a direct route, the client connects to the exit node without an extra relay node arranged by the service. That doesn’t mean there are no other network devices between the two ends, or that traffic takes the shortest route on a map. Public network interconnections and carrier routing still determine the path your connection actually takes. Direct routes in the same region can perform differently on different networks.

Compared with adding a relay or using leased capacity, a direct route typically has one fewer forwarding layer or dedicated-line resource, and its path is easier to understand. Try it first as a baseline for everyday browsing: open a familiar site, load image-heavy pages, submit a form or repeat an action after reconnecting. If your usual tasks work consistently, there’s no need to switch just because another route type has a more complex name.

Use-case checklist

Choose an International Route for Your Needs

Compare routes using real tasks, not just the client’s connection status. Where possible, use the same device and network, and note which step runs into a problem. Change only one variable at a time: route, protocol or network.

Everyday browsing

Start with the websites or apps you use most. If a service doesn’t require a specific region, try a nearby exit first and check the homepage, an image-heavy page and features that require you to sign in. If the homepage loads but some resources don’t, first check whether those resources follow the same routing rules as the main site; don’t assume the entire route is unusable. If several familiar sites slow down at the same time in the evening, compare with a relay in the same region. Avoid switching routes while submitting a form or saving work. Wait until the task is complete, then test again to avoid mistaking an interrupted session for a route failure.

Streaming and long-form video

First check which region the content is available in, then see whether the client shows a streaming label for the route. Test by playing the video itself, not just opening the homepage; try seeking and resuming playback, too, and watch for repeated buffering. A homepage that won’t load, a platform message saying content is unavailable, and a video that plays but keeps pausing are different issues. Check the connection, catalog and account requirements separately before deciding whether to change routes. If playback works well through an exit, start with that exit next time rather than switching repeatedly mid-stream.

ChatGPT and Other AI Tools

Choose an exit based on the tool’s service-region requirements, then test sign-in, sending a request and continuing a conversation. Seeing the homepage doesn’t mean the full workflow will work, and being able to send a message doesn’t guarantee a long response will arrive. If you use rule-based routing, check that page requests and sign-in requests follow the expected rules. If long responses repeatedly stop halfway, keep the account and exit region the same and retry with another route. If the tool reports a service issue, there’s no need to keep switching. For more checks, see AI Tool Connection Guide.

Online gaming

First check your account region, matchmaking region and voice chat requirements, then test routes in the same game region. Logging in or downloading an update successfully doesn’t guarantee a smooth match: downloads depend on sustained transfer speeds, while gameplay is more sensitive to sudden response-time changes, delayed inputs or choppy voice chat. Start with practice mode or a casual match, and pause background tasks such as syncing that may compete for bandwidth. If problems only occur when other devices at home are using the network heavily, check your local Wi-Fi too; not every fluctuation is caused by an international route.

Remote work

Check each work task separately: calls need reliable two-way audio, collaborative documents depend on saving and syncing, and remote desktops need responsive, continuous input. Before an important meeting, test your microphone, screen sharing and any documents you’ll need on the network you plan to use. Note a backup route in the same region. When accessing workplace services, follow your organization’s network and access requirements, and first confirm which sites should connect directly over your local network. If something fails, distinguish between account permissions, routing rules and the route connection before deciding whether to change the exit or contact your administrator.