90+ countries / 190+ routes

International routes and exit locations

Choose the region your service requires, then compare connection paths.
A city identifies the exit location; a route type describes how traffic reaches it.

IEPL Relayed Direct Unlimited devices
Browse route examples by region ↓

City Directory / CITY DIRECTORY

Browse routes by region

The city and route combinations below are examples to help explain regional selection, not a real-time availability list. Check the route list in your user dashboard for current exit locations, route types, and availability.

How to read the streaming column: “Check platform rules” means availability depends on the platform’s service regions, your account region, and the results on the current route. It does not mean every route supports every streaming service.

Swipe horizontally to view the table on narrow screens. The country/region and city describe the exit location; your destination does not need to be in the same city.

City and route type examples; check the dashboard for available routes
Country / region City Route type Streaming availability
Asia Pacific
JapanTokyoIEPLCheck platform rules
Hong KongHong KongRelayedCheck platform rules
SingaporeSingaporeDirectCheck platform rules
South KoreaSeoulRelayedCheck platform rules
AustraliaSydneyDirectCheck platform rules
North America
United StatesLos AngelesRelayedCheck platform rules
United StatesSeattleDirectCheck platform rules
United StatesNew YorkRelayedCheck platform rules
CanadaVancouverDirectCheck platform rules
CanadaTorontoRelayedCheck platform rules
Europe
United KingdomLondonRelayedCheck platform rules
GermanyFrankfurtDirectCheck platform rules
FranceParisRelayedCheck platform rules
NetherlandsAmsterdamDirectCheck platform rules
SwitzerlandZurichRelayedCheck platform rules
SwedenStockholmDirectCheck platform rules
Other regions
BrazilSão PauloRelayedCheck platform rules
South AfricaJohannesburgDirectCheck platform rules
United Arab EmiratesDubaiRelayedCheck platform rules
IndiaMumbaiDirectCheck platform rules

Connection Paths / ROUTE TYPES

Understanding dedicated routes, relayed, and direct connections

Route names describe how a connection is organized, not how fast it is. Consider your local network first, then how the connection performs between the exit location and the destination service.

IEPL

IEPL: Focus on the international segment

IEPL generally refers to an international transmission path built over an Ethernet private line. In route selection, it means dedicated resources are used for the cross-border segment. Your local connection to the access point and the path from the exit to the destination website still affect performance. An IEPL label does not mean the entire connection avoids public networks, nor that every app will perform the same way.

These routes may suit activities where consistent connections matter, such as extended remote work, video calls, or continuous streaming. To compare during peak hours, use the same network and destination service, and check page loads, audio and video continuity, and reconnections. Dedicated resources generally cost more to procure and maintain, but that does not directly determine any extra charge for a plan. Check the pricing page for plan details.

How to choose: Confirm that the destination service supports the exit region, then check whether the connection remains stable. A dedicated-route label is not a performance guarantee for every route.

RELAY

Relayed: Connect to an exit through an access point

A relayed route adds an access and forwarding stage between your local network and the international exit. Its purpose is to change how traffic enters the international path, not simply to add a location. If a direct route to an overseas exit is poor on a particular network, a suitable relay may provide a steadier connection. A congested access point or unsuitable route may offer no improvement.

For everyday browsing, cross-border work, or repeated access to the same service, compare a relayed route with a direct one. Keep the exit region the same where possible, so you do not mistake a change in region for a difference in route type. Relaying uses additional access and forwarding resources; costs depend on how those resources are arranged. An extra stage alone does not mean a route is necessarily faster or more expensive.

How to choose: Treat a relayed connection as an alternative access path. Judge whether it suits you by how your apps perform during the times you normally use them.

DIRECT

Direct: Primarily follows the path from your local network to the exit

A direct route generally means the client connects to the destination exit without an additional service relay. “Direct” does not mean there is only one physical link; traffic may still pass through multiple routers between network operators. Performance depends more on your local connection, carrier routing, and the network hosting the exit. A shorter geographic distance does not necessarily mean a better experience.

When the path from your local network to the destination region is smooth, a direct route can work well for everyday browsing, research, and general app access. It can also serve as a baseline for troubleshooting. Direct routes typically require fewer additional relay resources, but actual resource costs also depend on the exit location, data center, and network arrangements. This does not mean a direct plan is always cheaper or that direct is a lower-tier version of a dedicated route.

How to choose: Test with the tasks you actually do. If a direct route to the same region performs poorly, compare a relayed route or an IEPL option available in your dashboard.

Choosing by Use Case / USE CASES

Choose a route for your needs

The region determines where a service sees your exit; the route determines how the connection gets there. Meet the region requirements first, then compare performance to make troubleshooting easier.

Everyday browsing: Test sites you actually use

For research, reading, and web apps, start with a nearby region allowed by the destination service. Open pages you use regularly and check whether text, images, and signed-in content load fully. A slow page does not necessarily mean the entire route is having trouble; the website, a browser extension, or your local network could also be the cause.

Keep the client mode unchanged and switch only the route; adjust split-tunneling rules later if needed. Changing the route and mode at the same time makes it difficult to tell what helped. Once you find a suitable path, keeping a regular and a backup exit is more convenient than choosing from scratch every time.

Streaming: Check regional eligibility before playback

When choosing a route for Netflix or HBO, first check the platform’s availability in the target region, your account eligibility, and its content-region rules. Opening the platform’s home page does not mean every title will play, and different platforms may behave differently on the same exit. That is why the table does not claim that every route supports every service.

Once you have confirmed the region is suitable, play the content you actually want to watch and check startup, seeking, and playback continuity. If you see a region notice, check your account and exit region rather than repeatedly increasing video quality. A route can improve the connection path, but it cannot change content rights, membership benefits, or a platform’s own access rules.

AI tools: Check supported regions and session stability

Tools such as ChatGPT, Claude, and Gemini each have their own service regions and account requirements. Check the relevant platform’s current guidance before choosing an exit. Japan and other regions are not universally supported by every tool, and being able to open a website does not guarantee that account features will work. Confirm eligibility first, then check sign-in, prompt submission, and response delivery.

Keep the exit consistent during long conversations, file uploads, and active web sessions where possible. Frequent region changes may trigger re-verification and make results harder to compare. If something goes wrong, note the tool, the step where it happened, and the client mode, then follow the AI access guide to check each item. Do not use a route name as a substitute for checking the platform’s rules.

Gaming: Check which route handles game traffic

Games can be sensitive to connection stability and route changes, but working web access does not mean game traffic follows the same rules. Check the game’s supported regions and the client’s current proxy mode. Confirm whether the launcher, sign-in, and gameplay session use different paths. For a fair comparison, keep the game server and local network the same.

Do not treat any route type as a guarantee of dedicated gaming acceleration. If your browser works but the game does not connect, check app compatibility, rule matching, and the game’s official network requirements first. End your current session before switching exits to avoid mistaking an interruption caused by the network change for a route fault.

Work: Balance remote services and local resources

Remote work often involves company systems, shared files, meetings, and local resources such as printers. Follow your organization’s network-use policies and confirm whether third-party subscription services are allowed. If you already use a corporate networking tool, check for conflicts before making changes. Do not replace your existing work setup just to fix a single website.

When accessing international collaboration tools, compare session stability first and keep an exit that works reliably. For business systems available only in specific regions, regional requirements matter more than geographic distance. CitiVPN supports unlimited devices, but each device’s local network, system permissions, and rules still need to be checked individually.

Connection Checks / CONNECTION CHECK

Narrow down the issue before switching

Keep settings that work and change only the item you are testing. That makes results easier to repeat and simpler to explain to support.

Subscription and client

Update your subscription first, then check your plan status and current route list. Names in an older configuration may have changed, and saved exits may need to be selected again. Get the client and subscription from your user dashboard; do not mix unknown configurations into your current subscription.

Windows, macOS, iOS, Android, and Linux are supported. After signing in, you can get the client on Windows, Android, macOS, and Linux; iOS requires an active plan. Sign in to get your subscription, and see the getting started guide for import instructions.

View the Getting Started Guide →

Exit location and access results

After connecting, use an IP lookup page to help confirm the exit region seen by your browser, then check the target app. The result describes the request path used by that browser only; it does not prove that every app uses the same exit. Check your routing mode as well.

If every exit has the same issue, check your local network and client permissions first. If only one service is affected, check its region and account notices. When asking for help, share the error message and the step where it occurred; never share your password or full subscription link.

Check your current exit IP →