Call your ISP it looks like some of their IPs have a wrong geolocation. Maybe they recently aquired new IPv4 addresses that where previously located in eastern Europe.
Again, it's a major ISP, and I've been with them for the past 20 years. They've been using the same allocated IPs since the early Nineties - and EVERY detection services correctly assigns those IPs to my ISP, in my region.
You're right, a new IP from their pool should take care of this issue. Thing is, I'd like to know what could've possibly made Google think my current IP is in EE? what did I do to make Google Search - and ONLY Google Search think that?
Even if they did it's very unlikely they would peer in your town.
Geographic proximity isn't the main factor for peering and even if they did your session may still get terminated at a border network gateway in a big city and your traffic has to travel the same way.
I have a broken (parent transid verify failed on logical) btrfs RAID5 here that I can't mount anymore even with the recovery commands and google shows many results about it from less than a decade ago.
I don't think there's a way to check for sure but I'd say that's pretty likely. There are billions of android devices, and Linux servers, while popular, are probably less common just because servers are less common than consumer devices in general. But maybe I'm wrong!
[0]: https://github.com/cilium/pwru
reply