Server Locations, Filter by Region
From Asia-Pacific to Europe, every route is labeled with its route type and streaming support. Pick the one that truly fits your use case.
By Region View Routes
The following is a sample of available routes. The full 230+ routes can be filtered by region and use case in the client, with unlimited switching at no extra charge.
Asia-Pacific
8 Examples| Country | City | Route Type | Streaming |
|---|---|---|---|
| Hong Kong | Hong Kong | IEPL Dedicated | Netflix / Disney+ |
| Japan | Tokyo | Direct | Netflix / YouTube |
| Japan | Osaka | Relay | Disney+ |
| Singapore | Singapore | IEPL Dedicated | Netflix / Disney+ |
| South Korea | Seoul | Direct | Netflix |
| Taiwan | Taipei | Relay | YouTube |
| Malaysia | Kuala Lumpur | Direct | Netflix |
| Thailand | Bangkok | Relay | YouTube |
North America
6 Examples| Country | City | Route Type | Streaming |
|---|---|---|---|
| United States | Los Angeles | Relay | Netflix / Disney+ / HBO Max |
| United States | New York | Direct | Netflix / HBO Max |
| United States | Seattle | Relay | Hulu |
| United States | San Jose | Direct | YouTube Premium |
| Canada | Toronto | Relay | Netflix |
| Canada | Vancouver | Direct | YouTube |
Europe
6 Examples| Country | City | Route Type | Streaming |
|---|---|---|---|
| United Kingdom | London | Direct | BBC iPlayer / Netflix |
| France | Paris | Relay | Netflix / Prime Video |
| Germany | Frankfurt | Direct | Netflix |
| Netherlands | Amsterdam | Relay | Netflix |
| Italy | Milan | Direct | Prime Video |
| Spain | Madrid | Relay | Netflix |
Other
4 Examples| Country | City | Route Type | Streaming |
|---|---|---|---|
| Australia | Sydney | Direct | Netflix |
| Brazil | São Paulo | Relay | Netflix |
| India | Mumbai | Direct | YouTube |
| United Arab Emirates | Dubai | Relay | Prime Video |
Route Types Explained
Three route types correspond to different link quality and cost. Understanding the differences helps you pick the right route for each scenario.
IEPL Dedicated
An international Ethernet private line that establishes a dedicated physical link between two data centers, with carrier-grade bandwidth and latency guarantees. Traffic travels over a private channel rather than the public internet, so speeds stay stable even during peak hours. Ideal for 4K / HDR streaming, cross-border video conferencing, large file transfers, and other scenarios that demand maximum stability. It is the most expensive of the three types, and capacity is limited, so it is typically prioritized for high-bandwidth use cases.
Relay
Traffic is first forwarded through a third-party relay node before reaching the destination region. Relay nodes automatically probe route quality and avoid congested paths, effectively rerouting you to a smoother connection. Suitable for AI tools, streaming, daily browsing, and other scenarios where stability matters more than ultra-low latency. Moderate cost, balancing speed and price — a solid all-round choice for everyday use.
Direct
The destination data center is connected directly, with no relay node in between — shorter path, fewer hops, and typically lower latency. Suitable for gaming, latency-sensitive lightweight tasks, and scenarios that need speed but not heavy traffic. Lower cost and great value, though peak-hour congestion on the public internet may still affect performance.
By Use Case Choose a Route
Different use cases have different priorities. Here's a quick guide to choosing a route based on what you're doing.
Daily Browsing
Just pick the route closest to your physical location. Asia-Pacific users should prioritize Hong Kong / Tokyo / Singapore, North American users Los Angeles / New York, and European users London / Frankfurt. Both relay and direct routes work fine — no need to chase IEPL dedicated lines. If your network is unstable, relay routes are usually more reliable than direct ones.
Streaming
Prioritize IEPL dedicated lines. 4K streaming needs stable, high bandwidth; during peak hours, ordinary routes often slow down and quality drops from 4K to 1080P or lower. If no IEPL route is available in your region, choose a direct route and try to avoid peak hours. Streaming platforms check the geolocation of your exit IP, so you need a route in the corresponding region to access that region's content library.
AI Tools
Relay routes are usually more stable. AI tool requests involve large amounts of upstream and downstream data, and relay nodes can automatically optimize routing to reduce connection drops. Recommended: relay routes in Hong Kong / Singapore / Tokyo. If a connection fails, try switching to another route in the same region.
Gaming
Direct routes first. Gaming is latency-sensitive but doesn't need much bandwidth, so the shorter path of a direct route helps keep ping low. Choose a direct route in the same region as the game server — for example, Tokyo Direct for Japanese servers, Los Angeles Direct for US servers. If direct latency is still high, try a relay route; some relay routes perform better at certain times.
Work
IEPL dedicated or high-quality relay. Cross-border work involves video conferencing, file syncing, and remote desktop, all of which demand high stability. The dedicated link of an IEPL line avoids peak-hour congestion; if budget is limited, choose a relay route and avoid rush hours. For work, it's best to stick to one route consistently to avoid connection drops from frequent switching.
Coverage
The following is a partial list of coverage. The full list is shown in real time in the client.
Route Selection FAQ
What's the difference between route types?
Why do some routes not support certain streaming platforms?
Can I switch routes at any time?
How is the 120+ country coverage counted?
Find the Right Route for You
120+ countries / 230+ routes, plans from ¥9.9/mo, 60-day money-back guarantee. Sign up now and get started right away.
Start Free