My VPN Said Connected—So Why Was My IP Still in Canada?

The VPN showed a green Connected badge. The streaming app still said I was in Canada.

I was in a Montreal hotel trying to watch the Arabic commentary replay of Egypt’s World Cup match. I already had a regional sports subscription. I had also avoided social media all evening so I would not see the result before watching.

The VPN extension said it was connected to the region I needed.

The sports app disagreed:

This content is not available in your location.

I blamed the app first. I closed it, cleared its recent history, and signed in again.

Nothing changed.

Then I opened Google. The bottom of the page still showed Montreal.

I switched the VPN to another server and refreshed. Montreal remained.

Finally, I opened an IP-checking page in the browser launched by the hotel’s Wi-Fi screen. It showed a Canadian address belonging to the local internet provider.

The evidence seemed clear: the VPN claimed to be running, but neither my IP nor my country had changed.

The replay had already started. I had perhaps ten minutes before someone in the family group posted the score.

One “location” was actually three different things

The 2026 World Cup made this kind of confusion unusually visible.

A record eight Arab teams took part, while beIN held tournament rights across 24 markets in the Middle East and North Africa. Regional audiences were enormous, and travelers outside their usual broadcast area increasingly reached for VPNs to continue using subscriptions from home. (Beinsports)

That creates a simple expectation: select a country, connect, and watch every app on the device move there.

My hotel-room test exposed the problem with that assumption.

The IP address seen by a website is one kind of location. A phone’s GPS position is another. A search engine may also remember a location from account history, cookies, or permission settings.

Those signals can disagree without the VPN being completely inactive.

Before I could fix the streaming problem, I had to find out which traffic the VPN was actually carrying.

The green badge belonged to one browser

I had installed the established provider’s browser extension because it was quick.

The company itself was a sensible choice. It had years of public history, a large support operation, broad server coverage, and plenty of documentation. The extension took less than a minute to install, and the icon beside the address bar looked like proof that the laptop was protected.

It was not protecting the whole laptop.

A browser extension controls traffic inside the supported browser. Other browsers and standalone applications continue using their ordinary internet connection unless the provider’s full device app is active. (Privateinternetaccess)

That explained the Canadian IP address immediately.

The extension was connected inside Chrome. The hotel login page had opened my default browser, which was not Chrome. The sports service was running in its own application.

Changing servers inside Chrome could not change the IP address seen by either of them.

The green badge had been accurate. I had simply given it a much larger meaning than it deserved.

Once I understood that, the results stopped contradicting each other:

• Chrome was using the VPN extension.
• The default browser was using the hotel connection.
• The sports app was also using the hotel connection.

The match was blocked because the application that mattered had never entered the VPN tunnel.

Google was adding a second layer of confusion

Google still showing Montreal had made me more certain that the VPN was failing. In reality, the footer was answering a different question.

Google can estimate location from the IP address, device-location permission, account activity, saved places, and recent browser data. (Google) A VPN can change the network address without changing the phone’s GPS position or erasing the places remembered by a signed-in account.

That is why a map can still place a phone at the hotel even when browser traffic leaves through another country.

The same misunderstanding appears repeatedly in public VPN discussions: people expect a new IP address to move the GPS dot as well. (Reddit)

My mistake was similar. I had treated the Google footer as a clean VPN test when it was combining several location signals.

That distinction explained the label, but it did not solve the match. The sports app was still outside the protected route.

I needed a connection that covered the application itself, not another browser tab telling me that a server had changed.

More flags did not make the setup clearer

The established provider offered a full desktop application, so I installed it.

Under ordinary circumstances, its flexibility would have been useful. It included automatic selection, a long server list, several protocols, and enough settings to adapt the connection carefully.

With the family group becoming more active by the minute, it felt like another troubleshooting project.

I signed in again and selected a server. The hotel Wi-Fi interrupted the connection with another captive-portal screen. After I accepted the network terms, the client returned to automatic mode and chose a nearby Canadian exit.

The sports service remained blocked.

I reopened the server list, searched for the region, and tried again. The connection took long enough that I began checking whether the replay result had already appeared in my notifications.

The provider had plenty of countries. The problem was that I could not quickly tell whether the hotel portal had interrupted the tunnel, whether automatic mode had changed the exit, or whether the sports app had ever moved onto the new route.

At that point, the size of the server map stopped looking like the useful comparison.

I needed one clear connection that covered the device and completed the task.

I tested the application instead of the badge

I closed the extension and opened OnlydogVPN.

The smaller app organised its choices around situations rather than beginning with a dense map of countries. I selected the option for accessing a service while traveling.

Basic use did not require a conventional email-and-password account. There was no inbox confirmation, password creation, or second account login between opening the app and testing the replay.

I connected and repeated the checks in a more useful order.

First, I opened the IP-checking page in the default browser.

The Canadian hotel address was gone. A different public address and country appeared.

Then I opened the sports application.

The regional warning disappeared.

The replay page loaded, followed by the Arabic studio introduction I had been trying to reach. I dragged the timeline back to the beginning and switched the phone to silent before the family group spoiled the result.

The video played.

That was the test that mattered.

Not the color of a badge. Not the city written below a search page. The application that had caused the problem was now using the protected route and could play the content attached to my subscription.

The smaller app had removed several decisions from the process. I did not need to work out which browser was covered, return to a protocol menu, or watch automatic mode select another nearby server. I chose the task, connected the device, and reopened the app.

The country changed where it needed to change.

The search page no longer had to agree

Google still showed Montreal in one signed-in tab.

Ten minutes earlier, I would have taken that as proof that the VPN had failed. Now it was simply evidence that Google still knew the device’s physical or remembered location.

The independent IP page showed the new network route. More importantly, the sports application accepted it.

Those two observations answered the question I had actually been asking.

A VPN is not supposed to rewrite every location signal on a device. It changes the internet route and the public IP address seen by services using that route. GPS, account history, and saved browser data may continue pointing to the physical location.

The problem begins when the application you need remains outside the route.

That was what the browser extension had allowed. The smaller device-level app corrected it without turning the fix into another settings exercise.

The page was also making background connections

At halftime, I opened a match report to check the starting lineup.

The app’s blocked-request counter began increasing. The page was contacting services beyond the report itself, including advertising and tracking endpoints that the service filtered.

I could see the requests being stopped, but I could not inspect the service’s internal filtering rules or determine the purpose of every blocked connection.

This was not why the replay had opened. It was a smaller discovery afterward.

The location problem had already been solved. The counter showed that the app was also reducing some of the background requests surrounding the browsing session, giving me a reason to keep it installed after the match.

The service has fewer locations, a shorter public history, and fewer independent ratings than the established provider. Someone who regularly needs a highly specific city may still prefer a larger network.

But my first provider had already given me plenty of flags.

Its browser extension protected one browser while the service I needed was somewhere else. The full client then added enough server and connection decisions that I was still troubleshooting instead of watching.

The smaller app reduced the problem to one useful question: was the application I needed actually using the new route?

Once the replay opened, the answer was visible.

A VPN has not failed merely because a map or search page still knows where the device is. It has failed the immediate task when the app that matters continues using the old IP.

For me, the useful country was not the one displayed beside the VPN button. It was the one the match could actually see.