Cross-border access and international site acceleration Stable connections on international routes

How to read route types

An IEPL dedicated route is a point-to-point link that avoids congested public internet nodes, so jitter at peak hours is minimal — a good fit for meetings, live streams and long office sessions. Relay routes connect to the nearest entry point first and then hand off, taking a shorter path than direct connections, with price and stability in between; they are the most common everyday choice. Direct routes leave your local network straight out, cost the least, and suit quick research, downloads and anything that is not latency-sensitive.

Choosing routes by use case

For video, pick Japan, Hong Kong or Singapore routes marked as streaming-capable. For AI tools, prefer US or Japan routes and stay on the same route — switching mid-session can trigger re-verification. For cross-border work (email, documents, code repositories), prefer dedicated and relay routes: latency stays steady and long connections rarely drop.

How to read the route count

The route count is the number of available exit routes, not the number of countries. A single country usually has several routes across different cities and route types, so pick by city and type first, then by country. The 150+ routes are spread across 120+ countries, with exits in major cities in Asia, North America and Europe.

Switching and reconnecting

Staying on one route is more stable than switching often. If pages start loading slowly, switch to another route in the same region first, then consider another region; if it is still slow after changing regions, the local network is usually the cause — disconnect and reconnect once. Latency and bandwidth figures in the route list are reference values and vary with your local network and time of day.