Browse routes by region
The table below shows examples of region and route combinations. It is not a complete route list, and availability may change. City names help identify routes; they do not, by themselves, determine the content region a website will detect.
| Country/region | City | Route type | Streaming support |
|---|---|---|---|
| Asia-Pacific | |||
| Hong Kong, China | Hong Kong | IEPL | Verify by region and platform |
| China | Shanghai | Relay | Verify by region and platform |
| Singapore | Singapore | Relay | Verify by region and platform |
| Japan | Tokyo | IEPL | Verify by region and platform |
| Japan | Osaka | Relay | Verify by region and platform |
| South Korea | Seoul | Direct | Verify by region and platform |
| Australia | Sydney | Relay | Verify by region and platform |
| North America | |||
| United States | Los Angeles | Direct | Verify by region and platform |
| United States | Seattle | Relay | Verify by region and platform |
| United States | New York | Relay | Verify by region and platform |
| Canada | Toronto | Relay | Verify by region and platform |
| Canada | Vancouver | Direct | Verify by region and platform |
| Europe | |||
| United Kingdom | London | Relay | Verify by region and platform |
| Germany | Frankfurt | Relay | Verify by region and platform |
| France | Paris | Direct | Verify by region and platform |
| Netherlands | Amsterdam | Relay | Verify by region and platform |
| Sweden | Stockholm | Direct | Verify by region and platform |
| Switzerland | Zurich | Relay | Verify by region and platform |
| Other regions | |||
| Brazil | São Paulo | Relay | Verify by region and platform |
| Chile | Santiago | Relay | Verify by region and platform |
| South Africa | Johannesburg | Relay | Verify by region and platform |
| United Arab Emirates | Dubai | Relay | Verify by region and platform |
| India | Mumbai | Direct | Verify by region and platform |
| New Zealand | Auckland | Relay | Verify by region and platform |
Region names and traffic direction
Before choosing a route, distinguish which way you need to connect. If you are outside China and need to access content or business systems in mainland China, check the client's routes for access to China. For international websites, choose a route in the region supported by the target service. A region name such as Hong Kong alone does not indicate a route's direction. Check the route group, exit details, and your actual results.
Streaming support is listed as “Verify by region and platform” because network connectivity and access to specific content are separate questions. Platforms may consider account region, subscription entitlements, exit IP recognition, and content licensing. Results may also vary between routes in the same region. For a specific catalog or live event, connect and check the content directly; a region label is not a promise that it will play.
Route types and how they differ
IEPL, relay, and direct describe how a connection is routed, not how fast it is. Your experience also depends on your local network, exit location, and the destination service.
Illustration · Not a performance test
- IEPL
- Local connection → dedicated line segment → exit → destination service
- Relay
- Local connection → relay node → exit → destination service
- Direct
- Local connection → exit node → destination service
These diagrams illustrate route types. A route name does not mean every segment between your device and the destination service uses the same network.
IEPL: Focus on the stability of the dedicated segment
IEPL generally refers to an Ethernet international private line. The relevant segment uses dedicated-line resources to carry traffic rather than relying entirely on public-network routing. These resources typically cost more to build and maintain, making this option suited to tasks where sustained transfers, uninterrupted meetings, and peak-hour performance matter. An IEPL label does not guarantee the entire connection from your local Wi-Fi to the destination website; your local connection and the path beyond the exit still affect performance.
Choose based on whether the connection can handle your tasks consistently, not just on the route name. Check for repeated buffering while streaming, interrupted document sync, and choppy audio in meetings. If your local Wi-Fi is unstable, switching to a dedicated route cannot replace troubleshooting your local network. First make sure your device has a reliable connection.
Relay: A managed entry point for the onward route
A relay route sends your connection to a relay node first, then forwards it over the next link to an exit. The extra hop is intended to use a more suitable entry point and forwarding path; it does not simply shorten the distance on a map. Costs depend on the entry, forwarding resources, and exit, so the word “relay” alone does not tell you the plan cost or expected performance.
Relay routes are a useful starting point for everyday browsing, business access, and general streaming. If an entry point does not work well with your local network, try another route in the same region. Keeping the destination region unchanged makes it easier to tell a route issue from a region issue. The relay node itself may not be the region that the destination service detects; check the exit when verifying content region.
Direct: A simpler route structure, with performance shaped by routing
Direct usually means the client connects to an exit node without a separate service-side relay entry point. “Direct” does not mean the physical connection bypasses carrier equipment or that the route is shorter. The service-side path is relatively simple, but performance depends more on public-network routing between your local carrier and the exit, as well as the destination service's response.
When routing between your network and the exit is suitable, a direct route can work well for browsing, downloads, and general work. Results can vary significantly across network environments, so someone else's experience may not apply to your device. There is no fixed cost ranking between direct and relay routes that applies to every region. Check VPNFlat's actual prices on the Plans page; don't infer extra charges from route labels.
Choose a route by use case
Region is the starting point; consistently completing your task is what matters. Set your use case first, then compare routes in the same region to avoid changing too many variables at once.
Everyday browsing
If you don't need a specific region, start with a nearby region that offers suitable routing from your connection. Open the sites you use regularly and check that text, images, and sign-in pages load fully. If one site won't open, don't assume the whole route is down. Try other sites to see whether the issue is limited to that service or affects all access.
Once you find a route that works for everyday use, keep a backup in the same region. Switching exits frequently can trigger additional identity checks on websites and make troubleshooting harder. If your browser works but an app does not, check whether the app follows your system's proxy settings.
Streaming and video
Choose an exit based on the platform and content region you want, then check that your account includes access to that content. Opening the app's home page is not enough; play the program you intend to watch and check subtitles, audio, and playback continuity. If you see a region error, note its exact wording and compare other routes in the same region. Change one setting at a time rather than switching both video quality and region.
Streaming depends more on a stable, sustained connection than on a page loading quickly once. If playback buffers, pause high-bandwidth tasks on other devices, check your local network, and then compare routes. For more on content region detection and playback checks, see the streaming access guide. Always verify a specific platform after connecting.
AI tools and APIs
First check whether the AI service supports your selected region and whether your account is eligible to use it. Accessing the website successfully does not mean API requests use the same route; terminals, editors, and containers may have their own network settings. Test the website and the application making the actual request separately to distinguish connection failures from account permissions or service-side errors.
Keep the exit region consistent while working, rather than routinely switching regions. If a long response is interrupted, check local sleep settings, the client's background status, and application timeouts. Never include API keys or full authorization details in a support ticket. See the ChatGPT connectivity guide for more use cases.
Gaming and interactive apps
First check the game's server region and whether its client allows proxy connections, then choose an appropriate region. A website opening successfully does not mean the game process uses the same route. The launcher, updater, and live game may also follow different rules. Check support for the specific client rather than assuming compatibility based on the node's region.
When comparing routes, keep the game region and local network conditions the same. Check connection stability, disconnections, and in-game results. If the app has specific network restrictions, read its rules first. VPNFlat's route directory does not guarantee compatibility with every game or interactive app; verify each app individually.
Work and remote collaboration
Choose an exit based on your business system's region requirements, then check that meetings, file uploads, and document sync complete reliably. When accessing an organization's internal systems, follow its network policies. If you already use a corporate connection tool, check whether its routing rules conflict with the current client. Don't change business network settings just to force all traffic through the same route.
Before an important meeting or file transfer, test the connection on the same device and keep a verified backup route available. VPNFlat supports Windows, macOS, iOS, Android, and Linux, with unlimited devices. Local rules still need to be checked on each device; using the same account does not automatically give every device the same connection settings.
Connection verification steps
Check “connection established,” “requests took the expected route,” and “the destination service allows access” separately to pinpoint what needs attention.
Check your subscription and current route first
Check your subscription status in the user panel, then refresh the subscription list in your client and confirm that the selected route matches the region you need. Older lists may retain names that have since changed, so don't rely indefinitely on saved entries. Download the client and get your subscription through the user panel. Don't share your subscription link publicly.
For your first setup, follow the setup guide. No email address is required; a username and password are all you need. Choose a plan based on your everyday data use and how you connect. The number of routes in the directory does not represent extra data or dedicated resources. See the Plans page for plan benefits and billing terms.
Next, check whether the app is using the expected route
Check the client's connection status, proxy mode, and rule matches. If an app is not using the expected route, review its network settings and the client logs before refreshing the subscription again. If other network tools are running on the device, check for routing conflicts. On mobile devices, check background activity and battery settings so that an app suspended by the system is not mistaken for a route failure.
Finally, compare routes in the same region
Keep the destination service, device, and local network the same while comparing different routes in the same region. This lets you compare results without changing the content region. If only one service has a problem, note its error. If all websites fail, first check your local connection, client permissions, and subscription status. Change one variable at a time so your troubleshooting notes remain useful.
Choosing a route is an ongoing process of matching your connection to the destination service, not a one-time choice of route type. Keep the regions and routes you've verified on your own devices. If your location, network, or target app changes, repeat the same checks.