VPN connected but IP address hasn't changed: 9 fixes

If your VPN reports “connected” but the public IP has not changed, confirm the exact browser-visible IP before changing settings. Use the public IP check, save a baseline, connect the VPN, and compare in the same browser. This is distinct from a WebRTC, IPv6, or DNS question.

Nine focused fixes

1. Refresh the result rather than relying on an old tab or remembered city.
2. Compare the IP string, not just a country label.
3. Disable split tunnelling for the browser while testing.
4. Confirm whether you are using a browser extension rather than a device-wide app.
5. Disconnect and reconnect to a different server once.
6. Restart the browser so its network activity is fresh.
7. Check for a corporate or work VPN that intentionally routes traffic differently.
8. Compare IPv4 and IPv6 separately; a changed IPv4 does not settle IPv6.
9. Repeat in another browser or device on the same network.

Why cache is rarely the whole answer

An old page can create confusion, but a fresh IP request should show the browser’s current HTTPS exit. If the exact IP remains the baseline address after a reconnect, the app may not be routing this browser through a new exit. Read does a VPN hide your IP for the scope of that claim.

When the result is not really “unchanged”

A changed IPv4 with a visible familiar IPv6 belongs in IPv6 visible while VPN is connected. A public WebRTC candidate that differs from the ordinary IP belongs in the WebRTC workflow. If the same public IPv4 remains, use VPN connected but real IP is showing.

Bottom line

Change one variable at a time and test the address, not a badge. If the unchanged result is repeatable and the provider cannot explain the route, compare a service with documented app coverage and protection controls before switching.