IP route checks
If the VPN says connected but your visible IP does not change, the tunnel may not be carrying your default route, the profile may be split-tunneled, the connection may have failed silently, or the browser/tool may be showing cached information.
Use this guide when your OpenVPN client reports success but public websites still see your normal network.
Use the same tool both times and refresh after connecting.
Make sure general traffic is routed through the VPN.
Stale public profiles may connect without carrying traffic correctly.
Browser cache or DNS can confuse quick checks.
Open the IP check before connecting, write down the address, connect, then run the check again. Do not send the IP address to analytics or public reports.
A profile can create a tunnel but not push a default route. On Linux check ip route; on Windows inspect adapter route metrics; on Android reconnect the profile.
Some profiles intentionally route only selected networks. Public profiles are usually full tunnel, but you should verify redirect-gateway or pushed route behavior.
Choose a recently checked server with a fresh check time and known protocol/port before debugging deeper.
Refresh the page, use a private window, or compare another IP service if cached data looks suspicious.
Windows can retain adapter state, Android needs VPN permission for the intended app, and Linux routing should be checked with ip route.
Use the PublicVPNList IP check after import and again after disconnecting.