Region index

International Routes

Start with an exit location near your destination, then choose a route for the task. Try a direct connection for everyday browsing. If streaming, uploads, or calls keep dropping, compare relay and IEPL routes in the same region.

Regions and use cases

Find routes by region

Route types in the table are suggestions to compare first; a route type may not be available in every city. “Use cases” are tasks worth testing, not guarantees of access to a particular catalog, account region, or app.

Asia-Pacific
Country or regionRepresentative cityRoute types to compare firstUse cases
JapanTokyoRelayJapanese anime streaming
JapanOsakaDirectBrowsing Japanese websites
Hong KongHong KongDirectTesting game connections
SingaporeSingaporeRelayAsia-Pacific calls and collaboration
AustraliaSydneyDirectBrowsing Australian websites
South KoreaSeoulDirectBrowsing Korean news
North America
Country or regionRepresentative cityRoute types to compare firstUse cases
United StatesLos AngelesIEPLTesting long AI responses and uploads
United StatesSeattleDirectBrowsing technical documentation and news
United StatesSan JoseRelayWeb collaboration and file syncing
CanadaVancouverDirectEveryday access to websites on Canada's west coast
CanadaTorontoRelayEastern Canada websites and document collaboration
Europe
Country or regionRepresentative cityRoute types to compare firstUse cases
GermanyFrankfurtRelayFile collaboration with teams in Europe
United KingdomLondonRelayTesting UK websites and streaming
FranceParisDirectFrench-language news and public resources
NetherlandsAmsterdamRelayAccessing European cloud tools
SwedenStockholmDirectBrowsing Nordic websites
Other regions
Country or regionRepresentative cityRoute types to compare firstUse cases
BrazilSão PauloRelayBrazilian news and local websites
United Arab EmiratesDubaiRelayWeb tools for partners in the Middle East
South AfricaJohannesburgRelaySouth African websites and resources
ChileSantiagoRelayAccessing public resources in Chile

If a website does not require a specific exit region, start with a route near your current connection. If it does require a particular region, follow the service's rules and choose the corresponding location; there is no need to switch countries just to find a closer city.

Connection types

How do the three route types differ?

Route types describe the path between your network connection and the exit location. They do not determine how a destination website handles account access or regional restrictions. For a meaningful comparison, keep the exit region fixed and change only the route type.

Dedicated transport

IEPL

IEPL is an international Ethernet private line. A provider may use dedicated transport between the access and exit sides, but there is still a path from your device to the access point and another from the exit to the destination website. Choosing a private line does not mean the entire connection from your home to the website uses dedicated transport. If your own internet connection is unstable or the destination service is having an outage, a private line may not fix the problem.

Dedicated transport usually costs more than routes that use the public internet directly. It can be worth testing for tasks that are more sensitive to interruptions, such as sustained uploads, long calls, or long AI responses. Try it during a time when problems tend to occur, using the same device and task, then compare it with a relay route in the same region. Judge by whether you can complete the task, not by the route's name.

Forwarded through an access point

Relay

A relay connects to an access point first, which then forwards traffic to an exit in the destination region. The entry and exit points may be in different regions. For example, if the client labels them separately, use the exit location to determine the region shown to websites, not the entry point's proximity. A relay adds a forwarding leg; whether it improves performance depends on both the route from you to the entry point and the route from there to the exit.

Relays require access and forwarding resources to be maintained, so they usually cost more than direct routes; the actual difference also depends on the connection used. If a direct route opens a page but cannot finish a video or repeatedly drops a large upload, try a relay in the same region for comparison. If both routes fail at the same step, check the app or your local network before repeatedly changing exit locations.

Direct connection to the exit

Direct

A direct route connects the client to the exit side of the selected route over the public internet, without an additional relay entry point operated by the service. Public internet traffic still follows normal routing between providers, so a location that looks closer on a map is not necessarily reached by a shorter route. Performance at the same exit can vary by access provider and time of day.

A direct route has no dedicated forwarding leg and is usually the lower-cost transport option. For reading websites, looking up information, or using lightweight tools, keep it as your first choice if the pages you use load consistently. For gaming, compare a direct route in the region used by the game, then check controls, voice chat, and connection stability throughout a match before deciding whether to try a relay.

This section compares route transport costs, not prices by route name. See the Plans page for subscription prices and data allowances.

Use cases

Choose a route by use case

Compare routes using real tasks. Change one variable at a time: keep the device and local network fixed, then try a different route in the same region. If you see a region or permission message, check the service's rules instead of assuming every error is caused by the route.

Everyday browsing: check that pages load completely

For everyday access where no region is specified, start with a nearby direct route. Open websites you actually use, then go beyond the homepage to a page with images or another page in the site. This checks that page resources load too. The homepage alone can be misleading: opening it does not mean every step on the site will work.

If only one website fails to load, note whether it keeps spinning, reports that the domain cannot be resolved, or shows a login or permission page. The first two may point to a connection or DNS issue; a clear permission message means you should check your account access first. If several unrelated websites fail at once, check the client connection, proxy settings, and local network.

Streaming: check region and playback separately

First check the target catalog, account region, and content licensing, then choose an exit in the appropriate region. Opening a platform's homepage does not mean a particular title will play; seeing a title does not mean your account can watch it. Test the actual program you want to watch, checking playback start, seeking, and continuous streaming—not just whether its artwork loads.

If playback works but keeps buffering, compare a relay route in the same region, keeping the device, video quality, and test time as consistent as possible. If the player reports a region or copyright issue, check the platform's guidance first; switching cities is not a way to improve video quality. See the Streaming guide for common issues.

AI tools: test long responses and file uploads

First check which regions the tool officially supports and whether your account has access. After opening the site, try a short conversation with non-sensitive content, then test a long response or small file upload you would normally need. A successful login alone does not show that the connection is suitable for work. An interrupted long response could also be due to service load, file restrictions, or session state.

If the same task repeatedly gets interrupted, compare relay and IEPL routes in the same region. Keep the account, browser, and task content the same; start a new session after switching routes so an interruption in the old session is not mistaken for a problem with the new route. See the AI Tools guide for examples.

Gaming: match the game region, then compare connection quality

Choose a route based on the game's actual server region. The store region, account region, and match server are not necessarily the same. Test in a practice area or non-ranked mode first, checking that you can join a match, controls respond consistently, and team voice chat works. A smooth update download only confirms that the download worked; it does not replace testing in a match.

If problems occur only in the evening, compare direct and relay routes in the same region at the same time of day. Pause background downloads during the test to rule out local network congestion. If only the game fails while websites and other apps work, first check whether the game process is routed through the client before switching routes.

Work: troubleshoot calls, syncing, and access separately

For calls, start with a short test to check your microphone, video, and screen sharing. For file syncing, check that uploads finish and recipients can open the files. These tasks have different network requirements; a route that works for calls may not suit long uploads. Note call interruptions separately from file transfer failures so you know which task to retest next time.

If your workplace tools require a fixed exit, a specified connection method, or device authentication, follow your organization's access policies first. If your account reports that you do not have permission, changing routes cannot grant access. Retest on the day's network before important calls, and avoid switching exits during a call. When troubleshooting, record the app, time, route type, and exact error message.