VPN Connected but IP Address Not Changing?

You open the VPN app and it says connected. You visit an IP checker, expecting a new address, and the page shows the same one as before. It is a worrying moment, because the whole point of connecting was to see something different. The good news is that this symptom has a short list of ordinary explanations, and most of them can be separated from each other in a few minutes.

This article is about one specific question: the VPN shows connected but the IP address is not changing. It does not explain what an IP address is or how VPNs work in general; for those, see does a VPN hide your IP address first. Here we look at why the checker and the tunnel can disagree, in the order that is quickest to test.

Step zero: are you reading the right number?

Before touching any setting, make sure that what you saw is a genuine "before" and "after". Mistakes at this stage account for a surprising share of the reports.

• You did not note the original address. If you never wrote down the address from before connecting, you cannot know whether it changed. Disconnect, note the address, connect, check again.
• You compared different kinds of address. A checker may show an IPv4 address, an IPv6 address, or both. If you looked at IPv4 before and IPv6 after, the two will never match.
• The page was cached. Reload with a forced refresh, or open the checker in a fresh private window.
• You checked from a different device or network. A phone on mobile data and a laptop on Wi-Fi have different addresses by default.
• You used a checker that reads headers set by something else. A checker behind a corporate proxy shows the proxy's address, not yours.

Do the test again properly: disconnect, write down the number, connect, wait ten seconds, open a private window, and read the number again. Only then decide whether it has changed. If you need a more complete routine, the Help Center guide on checking whether your VPN is working covers it.

A decision table to find the cause

Match what you see with the most likely group of causes.

What you see	Most likely cause	Section
The app looks connected but sites run slowly or time out	Tunnel not really established	Cause 1
IPv4 changed, IPv6 shows your provider	IPv6 not covered	Cause 2
Only some apps show your old address	Split tunneling or app exclusion	Cause 3
Browser shows old address, other apps show new	Browser proxy, extension or cache	Cause 4
Address changed, but the city or country is odd	Location database lag	Cause 5
A different address, but your provider's name appears	Connected through a shared home or office network	Cause 6

The six causes, in the order to test them

Cause 1: the tunnel is not really up

Some apps show a connected state a moment before the tunnel can carry traffic, and some keep showing it after the tunnel has silently failed. If your phone has switched networks, put the device to sleep or lost signal for a moment, the app may not have noticed yet.

How to test: open a plain website and see whether it loads at normal speed. Then disconnect and reconnect from the app, and check the address again after ten seconds. If it now changes, the first connection was stale.

If the app keeps claiming it is connected without moving any traffic, update it, restart the device and review the Help Center guide on reconnecting when the VPN disconnects. If your pass has run out, the app can fail to connect at all; see how pass expiration works to check your remaining days.

Cause 2: IPv6 is showing through

Most checkers display the address your device used to reach them. Many home and mobile networks give your device both an IPv4 and an IPv6 address. If the tunnel carries IPv4 only, a browser may prefer IPv6 and reach the checker directly, so the page shows your provider's address even though the VPN is on. The IPv6 design is in RFC 8200, and the older IPv4 in RFC 791.

Signs: a long address with colons, such as one beginning 2001: or 2a, appears next to or instead of a short four-number one. The checker may even show two lines.

What to do:

1. Look at both lines on the checker. If IPv4 changed and IPv6 did not, you have found it.
2. Check whether the VPN app has an option for IPv6 handling or leak protection, and turn it on if so.
3. If it has none, you can turn IPv6 off on the network adapter for a test. This is a temporary measure, because some networks need IPv6.
4. Read VPN IPv6 leaks and the broader what is an IP leak for the full explanation.

Cause 3: split tunneling or an app exclusion

Split tunneling lets chosen apps skip the VPN. It is useful, for instance, when a banking app does not like VPN connections. But if the browser you test with is on the excluded list, it will show your normal address, and the VPN is working exactly as configured.

How to check:

1. Open the VPN app's settings and look for lists called split tunneling, excluded apps, allowed apps or bypass.
2. Note whether the list is an "only these apps use the VPN" list or an "all apps except these" list. They are opposites, and mixing them up is a common mistake.
3. Remove the browser or add it, depending on the mode, then reconnect and test.
4. On a computer, also check whether the operating system has its own per-app network rules.

The concept is explained in what is split tunneling. If you use it on purpose, remember that the excluded apps are exposed on whatever network you are on, which matters on public Wi-Fi.

Cause 4: the browser is on its own path

Browsers have a few ways to behave differently from the rest of the system.

• A manually set proxy. If the browser or operating system points to a proxy, the checker sees the proxy's address, whatever the VPN does. Look in the network or proxy settings and turn it off for the test.
• A browser extension that handles networking. Some extensions override the network path, and some privacy tools do too. Test with extensions disabled.
• Secure DNS inside the browser. This affects name lookups, not your address, but it can confuse results when you read a DNS leak page. See how DNS works.
• WebRTC. Browsers can reveal a local or public address through a feature used for video calls. A good checker will report it separately. Compare your result with a tool such as EFF's Cover Your Tracks to see what a website can learn.
• A stale tab. Close it, open a new private window and test again.

If one browser shows the old address and another application shows the new address, the VPN is working and the browser is the one with a special setting.

Cause 5: the location database is out of date

Sometimes the address really has changed, but the city or country shown looks wrong. A checker converts the address to a place by consulting a database, and those databases are built from registration records, traffic measurements and guesses. When a block of addresses is moved from one region to another, databases may take days or weeks to catch up, and different databases may disagree with each other.

This is not a tunnel failure. The test of whether the tunnel works is whether the address belongs to the VPN side rather than your provider, not whether a particular site names the right city. For a more detailed explanation, read why your VPN shows the wrong location. A practical tip: check two or three different checkers, and look at the organisation name they report, which is often more reliable than the city.

Cause 6: you are not where you think you are in the network

There are a few odd situations where the address looks unchanged because of the network layout rather than a fault.

• Your router does the VPN. If the VPN runs on the router and you also connect the app on your phone, you may be tunnelling twice or reading the router's address. Decide which one you are testing.
• A shared office or campus network. Some organisations send all traffic through a gateway whose address you see in both states. Ask the IT team before you assume a fault.
• A tethered laptop. The laptop's address depends on the phone's VPN state. Test from the device that runs the app.
• Two VPNs or a second security product. Another tool may take over the network adapter. Turn off the extras and test one at a time.

Three short stories

The quick comparison. Ravi connects, loads an IP checker and sees a long IPv6 address he did not recognise. He assumes the VPN failed. He reads further down the page and finds that the IPv4 line shows a new address. Turning on the app's IPv6 protection makes both lines match the VPN.

The banking exception. Joy added her banking app to the split-tunneling exclusion list months ago, and the browser was added at the same time by accident. Her checker shows her normal address. She removes the browser from the list, reconnects and sees a new address, while the banking app still works.

The odd city. Marco selects a location, connects, and the checker names a city three hundred kilometres away. He checks two other checkers and gets two more answers. All three give the same organisation. He concludes the tunnel is fine and the databases disagree, and carries on.

A short routine to follow

1. Disconnect and note the address, both IPv4 and IPv6.
2. Connect, wait ten seconds, open a private window and recheck.
3. If nothing changed, disconnect and reconnect once, then restart the app.
4. Check the split-tunneling or excluded apps list.
5. Check for a browser proxy or extension.
6. Check the IPv6 line and the app's IPv6 or leak option.
7. Try a second checker and a second browser.
8. Restart the device, and update the app.
9. If still unchanged, contact support with the device, the network type, which line (IPv4 or IPv6) stayed the same and what you tried.

Limits and common mistakes

• Treating the city name as proof. The organisation and the address matter more.
• Expecting a new address on every connection. Assignment varies.
• Turning off protections permanently after a test. Restore them.
• Reading a checker through another proxy or security product.
• Assuming a changed address means anonymity. Accounts, cookies and device details still identify you; see can you be tracked with a VPN.
• Forgetting the login. Use the username and password on your My Pass page if the app asks again.

Summary

When the VPN says connected but the address does not seem to change, first make sure the comparison is fair, then look for IPv6 showing through, split-tunneling or app exclusions, browser-level proxies and extensions, and finally database errors in the location that is displayed. Fix them one at a time and retest in a private window.

If you want a simple way to protect each device on its own, the pricing page shows how a prepaid pass works.