Global Route List

For research and reading, start with an exit that works with your target service and performs well on your local network. Open your usual sites and check that images, search, and account pages all load normally, then keep that route for everyday use. A homepage loading successfully doesn’t mean every resource will work; images, scripts, and attachments may come from different domains.

If only a particular page has issues, first check whether the client’s routing rules cover that domain; there’s no need to switch the entire region right away. Your browser may also temporarily reuse an existing connection through the old exit. After switching routes, reopen the page before evaluating the result. This is more useful than rapidly trying multiple nodes.

Services such as Netflix, Disney+, YouTube, and HBO have their own content libraries and account rules. First identify the service and region you need, then choose the corresponding exit. Reaching the site, seeing its catalog, and successfully playing content are separate steps; check each one. Playback issues can also relate to licensing or account access, so the page language alone can’t tell you whether a route is suitable.

During playback, check for ongoing buffering, repeated changes in video quality, and whether playback resumes after pausing. If you need to switch routes, compare options in the same region first so you’re not changing both the content library and network path at once. For troubleshooting steps, see Streaming Guide →

Before using tools such as ChatGPT, Claude, or Gemini, check the service’s requirements for accounts, location, and eligibility. A route provides network connectivity; it doesn’t override the service’s own access requirements. Once you’ve chosen a suitable region, try to keep the same exit throughout a session to reduce disruptions from repeated logins or changes in location detection.

When testing, don’t stop at the login page. Also check that you can send prompts, view replies, and upload files. If the website works but the desktop app doesn’t, first check whether both use the same routing rules. Avoid switching routes frequently during long tasks. If an error occurs, keep the message so you can distinguish a service-side restriction from a connection issue.

Gaming depends more on latency variation, packet loss, and connection stability during interactions; web download performance is not a substitute. First confirm the game server’s region, then check that the client supports the connection method the game requires. Proximity to the server is only one screening factor: routes may take a detour, so test in the actual game.

When comparing routes, keep the game region and local network connection unchanged. Check that voice chat, the launcher, and the game itself all use the expected route. This service is a network acceleration subscription; general route labels are not a promise of game-specific optimization. If the game doesn’t support your current network setup, follow the game’s and client’s instructions.

Video meetings, shared documents, and work platforms need a stable connection. Before starting a task, test login, document saving, file uploads, and meeting audio and video—not just whether the platform homepage opens. Company systems may have requirements for exit IPs, device identity, or access regions. Follow your organization’s network and information security policies before use.

Keep a route you’ve already tested for the duration of a task, and have an alternative in the same region ready. Unlimited devices describes the number of devices you can use; it doesn’t mean multiple devices can transmit at once without sharing local network resources. If performance varies between devices, check the network connection, client settings, and background tasks before switching routes.