Read the network details presented by your current connection to verify the route exit, ISP, and proxy status. Queries pass only through this site’s same-origin API.
Results come from the public network exit used when this browser made the request. After switching routes, run the check again to compare whether the reported location changes.
Reading network details through this site’s API…
Your public IP is the address websites see. After connecting to an international route, the result should generally match the exit location of the selected route. If the original network still appears after switching routes, disconnect first, reconnect, and run the check again.
The reported location comes from an IP address database and indicates an approximate exit location. Databases may take time to update, so use this result as a route-checking reference—not as your device’s location or precise geolocation.
This field identifies the network operator or autonomous system associated with the public exit address. When traffic passes through a data center, transit network, or dedicated-line exit, the displayed name may differ from the local access network. This is a normal routing-level difference.
The proxy status is returned by this site’s diagnostic API. Detecting a proxy does not mean the connection is faulty; it only indicates proxy-network characteristics at the current exit. No detection does not mean every website will reach the same conclusion, since each service uses its own identification rules.
Your public IP and DNS requests may take different paths. This page reads only public network details, so a single IP result cannot determine whether DNS requests are traveling through the expected route.
Run a check while no accelerated route is enabled, and note your current network location and ISP. Use the result for comparison later; there is no need to disclose or submit it to another service.
After connecting, click “Check Again.” Confirm that the public IP and country or region have changed and broadly match the route direction selected in the client.
Check whether your system, router, and browser have separate DNS configurations enabled. If multiple configurations are active, keep the one consistent with the current route setup, then disconnect and reconnect.
If the exit location is correct but access results still differ from expectations, restart the browser, refresh the system network state, reconnect the client, and check whether split-routing rules are sending related requests through the local network.