[kybernetyk]

Some weeks ago Google started to consider my server I use as an exit point for VPN to be located in Iran. (It's in the Netherlands). Thus I couldn't access Google apps for domains, my adwords account, etc. as long as I was using that server.

Contacting Google's support brought the expected results and in the end I had to get a new IP assigned to the machine.

I have no idea how the IP got flagged as an Iranian one. Every geolocation service and whois stated clearly it's a dutch IP managed in the Netherlands. I only found out what was going on when I logged into my normal non-apps gmail account and looked at the activity list (I assumed I have been hacked). It showed one active session: my IP with origin "Iran".

/story time

[MichaelGG]

Once again, Google thinks my Denver IP is in Hungary. A year so it was France, but then they went back to Denver. Whatever system they use is obviously flawed. A simple ping would reveal it's incorrect, even. Every other source from Microsoft to Netflix to random geo IP lookups get it right.

This wouldn't be that bad, except Google is aggressively anti-user when it comes to this stuff, overriding both your headers and OS settings. (And alt text on things like Google Doodles always show up in the "geo" language, regardless of any overrides. Fortunately I bounce all my Google queries via disconnect, so this doesn't impact my search experience, just other Google sites usage.