The lookup runs as soon as the page opens: current exit IP, country and region, ISP and proxy signals. Results come from our own endpoint and show whether the client has actually switched to the selected route.
Checking…
Checking…
Checking…
Checking…
Checking your current exit…
Results are shown for this visit only. They are not saved to your account and say nothing about route quality. If you see “Temporarily unavailable”, the endpoint is most likely unreachable for a moment — just check again shortly.
The four fields answer three questions: where the exit is, who provides it, and whether it carries proxy or data-centre signals.
This is the source address a destination site records — the exit your client is using right now. Check again after switching routes and the address should change. If it stays identical before and after connecting, traffic is not going through the selected route; go back to the client and confirm the connection state.
Location is inferred from the registration details of the IP block, down to country and city — never a street address. Some routes are registered somewhere other than where the data centre actually sits, so treat this as a reference only; streaming and AI platforms make their own regional judgements.
Common exit examples; routes cover 110+ countries and regions.
This field shows the ISP or data-centre name registered to the IP block. Home broadband usually shows a local ISP; dedicated and relay routes usually show a data centre or cloud provider. A change of name is not an anomaly in itself — it reflects the network the exit sits on, not route quality.
Some platforms judge whether an exit is a proxy or data centre by the type of its IP block. “Proxy signals detected” means the block has been flagged in a public database; it does not mean the route is unusable. For services that are picky about exit type, another route may return a different result.
The exit address only tells you where traffic leaves from. Which channel resolves your domain names is a separate question — four steps will confirm it.
Disconnect the client, press “Check again” on this page, and note the IP, country/region and ISP. That is your local baseline for comparison.
Connect to the route you want and check again here. The IP should change to the route's location, and the ISP field usually switches from your local broadband to a data-centre name. If both change, traffic really is going through the route.
Look at the DNS settings in your client and make sure resolution goes through the route rather than your local ISP. If the client offers switches such as “remote DNS” or “DNS follows route”, turn them on and test again. If resolution still uses local DNS, streaming services may serve content for your local region.
WebRTC in the browser can connect directly, outside the route, and expose your local address to the other side. Disable it for the browser in your client rules, or block it in the browser's site permissions, then check again.
The exit IP already shows the route's location, yet a streaming service still says the region is wrong. Most often resolution is still handled by the local ISP, or the browser has cached the previous region's result. Clear the cache first, then review the DNS settings as in step three.
What this page receives and what it keeps — stated plainly.
A lookup request is used only to return the result to the current browser. Results are not written to your account, not tied to a subscription, and not counted in any page analytics.
The page does not poll in the background; a result is produced only when you press “Check again” or reopen the page, and the previous result is gone after a refresh.
No. Location comes from the registration details of the IP block, down to country and city; it cannot pinpoint a street address. The same block may be registered slightly differently across databases, so small differences in the level of detail are normal.
First confirm your current network can load this page at all, then press “Check again”. Repeated failures usually mean the endpoint is temporarily unreachable — unrelated to whether your client can connect to a route. Try again a little later.
No. It only means the IP block has been flagged as data-centre or proxy type in a public database. Most sites do not block on that basis; for services that are picky about exit type, another route may return a different result.
Results appear only on this page. They are not written to your account or tied to a subscription, and they are gone once you close or refresh the page.
Once the exit checks out, the usual next steps are reviewing routes and plans, or importing the client for your platform.