Global servers
Routes are grouped by Asia-Pacific, North America, Europe and other regions, with each entry noting the city, route type and the streaming platforms it usually pairs with. No latency or load figures appear in the table: route status changes daily and a static table can't stay accurate — choosing by route type and city is more reliable.
Swipe the table sideways. Route type decides whether a connection holds up at peak hours; city decides which streaming region and which services you land in. Those two are worth more attention than the number of servers.
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| Japan | Tokyo | IEPL dedicated | Netflix / Prime Video |
| Japan | Osaka | Relay | Netflix / YouTube |
| Hong Kong | Hong Kong Island | IEPL dedicated | Netflix / Disney+ / YouTube |
| Hong Kong | Tsuen Wan | Relay | YouTube / Prime Video |
| Singapore | Singapore | Direct | Netflix / Disney+ |
| South Korea | Seoul | Relay | Netflix / YouTube |
| Malaysia | Kuala Lumpur | Direct | Netflix |
| Thailand | Bangkok | Relay | Netflix |
| Australia | Sydney | Relay | Netflix / Disney+ |
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United States | San Jose | IEPL dedicated | Netflix / Disney+ / Hulu |
| United States | Los Angeles | Relay | Netflix / Hulu / HBO Max |
| United States | Los Angeles | Direct | YouTube / Prime Video |
| United States | New York | Relay | Netflix / HBO Max |
| Canada | Toronto | Relay | Netflix / Prime Video |
| Mexico | Mexico City | Direct | Netflix |
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United Kingdom | London | Relay | BBC iPlayer / Netflix |
| Germany | Frankfurt | IEPL dedicated | Netflix / Disney+ |
| France | Paris | Relay | Netflix / Prime Video |
| Netherlands | Amsterdam | Direct | Netflix / YouTube |
| Italy | Milan | Relay | Netflix / Prime Video |
| Spain | Madrid | Direct | Netflix |
| Sweden | Stockholm | Relay | Netflix |
| Country / Region | City | Route type | Streaming |
|---|---|---|---|
| United Arab Emirates | Dubai | Relay | Netflix |
| India | Mumbai | Direct | Prime Video / Netflix |
| Turkey | Istanbul | Relay | Netflix |
| Brazil | São Paulo | Direct | Netflix |
| South Africa | Johannesburg | Relay | Netflix |
The difference between the three types isn't whether they connect, but which path the traffic takes, whether it gets squeezed at peak hours, and what a unit of bandwidth costs. Sorting those three out before you choose is faster than trying routes one by one.
IEPL is an international Ethernet private line: the carrier provides a fixed-bandwidth channel at both ends, and traffic from entry to exit never crosses the public internet's international gateways. Its value isn't peak speed — it's that when everyone is crowding the public gateway at peak hours, this channel's bandwidth has already been reserved.
Built for long sessions that can't drop: 4K video, transoceanic video calls, large file sync. The trade-off is the highest cost per unit of bandwidth, so dedicated lines are the smallest group on the list, usually only in hub cities such as Tokyo, Hong Kong Island, San Jose and Frankfurt.
A relay route has two legs: the client connects to an entry node near it, and that entry node forwards over an optimised backbone link to the exit node. The client-to-entry leg runs over the public internet; the entry-to-exit leg runs over the optimised link, so congestion at the local gateway is confined to the first leg.
The upside is flexibility: with plenty of entry nodes, switching entry often sidesteps congestion at your local ISP, and the exit can be picked per platform region. This is the largest group on the list, and a relay route is enough for most everyday use.
The cost is one extra hop, so the first packet is slightly slower than direct. You can feel it in latency-sensitive work; ordinary web browsing mostly can't.
Direct means the client connects straight to the exit node with no second forward. Shortest path, fastest handshake — well suited to web browsing, API calls and AI tool chats, where there are many requests and little data per request.
The limit is that the cross-border leg runs over the public internet's international gateway, and quality depends on your local ISP's gateway that day. Peak-hour swings are more visible than with dedicated or relay routes, and long 4K sessions make the difference easy to see.
Direct is the cheapest, usually placed in regions close to users with stable gateway quality. It works well as the default route, moving up a tier when problems appear.
Pick the exit country first, then the route type, then switch cities within the same type. That order is much faster than trying routes one by one, and easier to repeat — next time the same problem shows up, just walk the same steps.
Many requests, little data each: a fast first packet matters more than peak bandwidth. Start with direct and an exit near you; if pages slow down noticeably at peak hours, switch to a relay route in the same city.
Recommended: direct → relay4K and Dolby Vision need far more bandwidth headroom than 1080p, and jitter hurts the picture more than the headline speed. Prefer IEPL dedicated, with the exit chosen by platform region; if you only get low resolution, try another route in the same city first.
Recommended: IEPL dedicatedA long conversation is a steady trickle of small traffic, so stability beats peak speed. Direct or relay both work; keep the exit country consistent with the tool account's region. Interrupted replies usually happen when the route switches, so staying on one route is steadier.
Recommended: direct / relayWhat matters is stable round-trip latency, not bandwidth. Prefer relay, with an entry node as close to your local ISP as possible; within a type, picking the entry city works better than picking the exit city.
Recommended: relayMeetings hate dropping mid-call, and bandwidth needs headroom. Prefer IEPL dedicated; one account covers unlimited devices, so when a phone and a laptop are online at once, the dedicated line's bandwidth guarantee matters more.
Recommended: IEPL dedicatedAfter switching, don't rely on the client's Connected status alone — confirm the exit separately. Walk the five steps below and most problems can be pinned to a specific link in the chain without reinstalling anything.
Open the My IP page and compare the exit country and city it shows with the exit you selected. If they differ, the connection never actually switched, and further troubleshooting is pointless.
Once the exit is right, open the target platform and check whether the region's catalogue changed. If not, retry once in a private window to rule out local cache; if it still doesn't change with the cache cleared, then suspect the route.
If the exit is correct and the platform still says the region is wrong, it's most likely an account region or payment region that doesn't match the exit. Switching routes won't fix that — go back to the account settings and check.
Disconnect and reconnect once; if it's still wrong, switch to another route in the same city; if the whole city fails, move to a neighbouring city. Change one variable at a time so you know which step did the work.
Fine by day, slow at night usually isn't a misconfiguration but congestion at your local gateway. Moving from direct to relay, or from relay to IEPL dedicated, works better than reconnecting over and over.
For a more detailed troubleshooting order, see the FAQ; for each platform's region rules, see the streaming guide.
The full list is shown in the client grouped by continent; only common regions are sampled here. The table above lists some of those cities — the same country usually has other cities available.
No email address required — a username and password are all you need to create an account. Plans from ¥9.9/month with 60GB; data packs never expire; 30-day money-back guarantee.