Google shows old country after GL.iNet reset

Hi all,

I’m seeing a weird issue with my GL.iNet router:

  • Now connected via Wi-Fi to my ISP internet in my home country (not using VPN).

  • Previously used abroad with WireGuard VPN and “block non-VPN traffic” enabled.

  • After a GL.iNet reset, Google shows the old country for any device connected to the GL.iNet, even though my IP is correct.

  • IP-based services (IP2Location, Microsoft) show my home country correctly.

  • No DNS leak — all IP check websites show my correct country.

  • I tried changing Wi-Fi name and MAC address, but it didn’t help.

Observation:

  • Google seems to track Wi-Fi MAC, SSID, device/browser history, and account activity, not just IP. Historical activity abroad can temporarily affect location.

  • I’ve used the GL.iNet router abroad many times, but this is the first time I activated location services on several phones connected to it, which may explain the sudden behavior.

  • On those phones, switching to 5G immediately shows the correct country in Google search.

Questions:

  • Should I disable the GL.iNet Wi-Fi access point so nearby devices don’t report its location? I’ve left Wi-Fi on before without issue.

  • How long does it typically take for Google to update the Wi-Fi mapping?

  • Has anyone found a faster way to clear Google’s cached Wi-Fi location?

WDYT?

Either the GEOIP information for your IP (likely out of your control) is wrong, you are connected to a VPN, or you have an old cookie in your browser. The router should not be dictating this by itself.

ETA: One other consideration is that your DNS configuration could also be causing this issue.

It seems like Google is messed up — now, on two different devices, connecting to my ISP router (via Wi-Fi or Ethernet) still shows the wrong country in Google Search. Event activate GPS doesn't change much! Google is still considering wrong infos!

Yes, Google is using WiFi SSID for location tracking. I’ve had this issue when I used my home SSID for more than 2 weeks outside. My systems got very confused on my location.

In my observation this association is faster, when only a few SSID are around.

Solution: just wait some days, until Google is tracking your SSID where it is, again. It helps when you are leaving the SSID range every now and then, so the devices needs to fall back on different methods.

But if you want to keep Google from this behaviour, you could add _nomap to the SSID, because Google is in general very transparent on their work. See Control access point inclusion in Google's Location services - Google Maps Help

1 Like

Thanks @LupusE . Now it does make sense. I’ll wait a few days and see how it goes.

When this happend to you, did you use GPS earlier on one device that was connected to your travel router?

I’ve read somewhere that phones report near by WIFIs location even without connecting to them.
But I used this router many times and I always had its WIFI activated. Near by devices never reported the location to google location services.

It’s only this time when I used GPS on my mobile while connected on mobile data. I think I left the phone GPS ON when I came back near the GL.Inet router. That was the reason.

So it’s a bit ambigious when/how phones report to google location services(when not being connected to them). I’ve never used that suffix.

I am using my phone for Google Maps and Osm a lot. I never turn off Wifi, GPS or Bluetooth, even if some articles about security suggest this.

Using WiFi RSSI was a test at first, if it could be used as additional location in areas with bad GPS, because of high buildings … it went well and they added it to their location system.

Yes, you don't need to be connected, the SSID just needs to be visible.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.