Server locations and route distribution

In practice the three work together: relay by default, switch to a dedicated line for long connections or meetings, and use direct for one-off downloads. In the client you can set rules per app rather than sending everything down a single route.

• 01

  Everyday browsing and search

  Start with the nearest relay entry. For users in Chinese-speaking regions, Hong Kong and Tokyo are only a few hops away, and page loads spend most of their wait on DNS resolution and time to first byte — a relay entry shortens exactly that part. If you are only looking things up and reading docs, direct is enough; no need to tie up a dedicated line.

  Routes to try: Hong Kong IEPL dedicated lineTokyo relay

• 02

  Streaming

  First work out which region's library has the title you want, then pick the matching exit. Netflix's US, Japan and Hong Kong libraries differ, and Disney+ Singapore differs from Disney+ US. Pick the wrong exit region and no route will show you what you want. Once the region is set, prefer a relay in that region — it holds up better at peak times.

  Routes to try: Los Angeles relayTokyo relaySingapore direct

• 03

  AI tools

  Stick to one route; don't switch constantly. Most AI tools record the region you sign in from, and jumping across several countries in a short window tends to trigger extra verification, which is more hassle, not less. Pick a stable relay or dedicated line and keep using it — far less work than hunting for "the fastest one" every time.

  Routes to try: Hong Kong IEPL dedicated lineFrankfurt IEPL dedicated line

• 04

  Gaming

  Look at hop count rather than exit region. Competitive games are sensitive to round-trip latency, and every extra hop adds delay. Choose the shortest direct or single-hop relay path and avoid peak hours where you can. If the game servers are in Asia Pacific, nearby Tokyo or Seoul usually beats a distant exit.

  Routes to try: Tokyo relaySeoul relay

• 05

  Remote work and file transfer

  For long-lived connections, prefer a dedicated line. Video meetings, code repository syncs and large uploads all have to start over if the stream drops, and a dedicated line's fixed path and lower jitter mean fewer reconnects. On a tighter budget, switch to the dedicated line only for meeting hours and use relay the rest of the time.

  Routes to try: Hong Kong IEPL dedicated lineFrankfurt IEPL dedicated line

A suggested order: run the default relay entry for a day and note the times when it feels worse; then switch to a dedicated line or a different exit region for those windows. Change one variable at a time — if you change both the route and the exit at once, you can't tell which one made the difference.

The table on this page lists representative samples only; the full list expands by region in the client, where you can filter by exit region and connect directly. You don't need to try them one by one — pick two or three using the order in the previous section, then narrow down to one based on how it actually feels.

• East Asia
• Southeast Asia
• South Asia
• Oceania
• North America
• Latin America
• Western Europe
• Northern Europe
• Southern Europe
• Central Europe
• Eastern Europe
• Middle East
• Africa

Exit IPs are assigned by the data centre and may change when a carrier adjusts routing or the data centre carries out maintenance. If you need an IP added to an allowlist, confirm your requirements before choosing a plan rather than assuming the exit address will stay the same.