This page reads your current network exit through a same-origin endpoint, showing the IP geolocation, ISP, and proxy detection result. Run the check before and after connecting a route to see more clearly whether your exit has changed.
Network information is temporarily unavailable. Check your connection and run the test again; this page will not substitute results from a third-party public endpoint.
Your public IP is the network address websites actually see; the location and ISP come from public registration data associated with that address. Consider all results together rather than relying on just one.
When your browser visits a website, the site typically uses your public IP to identify the network source. If the result changes after connecting a route, the page request is being sent through a new network exit. The copy button copies only the IP returned by this request; it does not add to or infer missing data.
The location is the IP database's assessment of where the exit address is registered, not the device's physical location. After switching routes, use it to check whether the exit is in the intended region. Databases can lag behind current assignments, so assess city or regional discrepancies alongside the connection status and actual access results.
The ISP field identifies the network organization associated with the IP. A change in ISP before and after connecting usually corresponds to an exit change, but databases may use a carrier name, network organization, or autonomous system name. Different wording does not necessarily indicate a connection problem.
This field shows whether the GeoIP data source classifies the current exit as a proxy network. The result may change as records are updated and may vary because of shared exits, data-center networks, or route types. It is useful for troubleshooting, but does not mean a website will necessarily accept or reject the connection.
A GeoIP lookup shows only the exit used for web requests. Checking for DNS leaks also requires verifying which servers handle domain-resolution requests. These are separate parts of the connection, so a normal public IP does not automatically mean the DNS path is correct.
Disconnect the acceleration route, review the DNS settings in your system's network details, and record the current exit region. This gives you a baseline for comparing the connection afterward.
Connect to the target route and refresh this page to confirm that the public IP matches the selected region. Then review your system or client network diagnostics to see whether the DNS path changed with the connection.
If the exit is in the target region but the DNS server continues to point to your original network provider, reconnect the route, close and reopen the browser, or check for custom DNS settings on your system.
Save the public IP, route name, and client diagnostic results, then submit a ticket through the user panel. Do not paste subscription links, passwords, or other account credentials on public pages.