Google.com being redirected to google.com.hk on linode.

I'm not seeing it. My Linode is in Atlanta.

At least one other person (#linode on freenode) saw the behaviour, he/she was getting pushed to google.co.za.

Visiting www.google.com/ncr fixed it for me, for now.

@Kint:

At least one other person (#linode on freenode) saw the behaviour, he/she was getting pushed to google.co.za.

I've been getting directed to google.ca (Canada) and my Linode is in Newark.

@carmp3fan:

I've been getting directed to google.ca (Canada) and my Linode is in Newark.

At least you can read the results :)

try www.google.com/ncr in the meantime.

And I'm being redirected to google.pl. My linode is in UK.

My Linode is in London and I am being redirected to google.com.hk

My node in Fremont is being sent to google.co.au

Report it here.

@OverlordQ:

My node in Fremont is being sent to google.co.au
Ditto :-)

@sweh:

@OverlordQ:

My node in Fremont is being sent to google.co.au
Ditto :-)

my fremont 'node goes to google.com.hk.

Mine is in London and is getting redirect to google.ru

@carmp3fan:

I've been getting directed to google.ca (Canada) and my Linode is in Newark.

ditto

My Linode is in the UK.

Using it as a ssh proxy and http://www.google.com/ redirects to http://www.google.com.hk/

Turn off the proxy and it works fine.

What's going on?

Mine's in Newark and I'm currently getting google.de.

See this page for information on working around the problem.

It seems as if they're now guessing the country based upon what other nearby IP addresses do; if a user from 192.0.2.105 consistently acts as if they're in India, it seems logical to assume that 192.0.2.105 is in India. It's not a huge stretch to think that 192.0.2.104 and 192.0.2.106 are in India, too. This seems arbitrary, but when you think about it, is the physical location of the Linode equipment any less arbitrary?

My solution: stay signed into Google. They fix my location by asking my web browser to report the signal strengths and BSSIDs of nearby wireless access points; no guesswork there. It is kind of creepy getting targeted ads depending on whether I'm in the bathroom or the kitchen, though.

I'm also having this issue and sent a request to google.

http://www.maxmind.com/app/lookup_city knows that my IPs are in Dallas, not sure what's up with Google.

Hi, I'm a Linode customer and a Google employee. Several of Linode's blocks of IP addresses were definitely getting bogus geolocation results. Thanks to some help from Linode's support folks, I got all the blocks that had bogus entries reported internally at Google, and everything should be fixed.

Different applications at Google get geolocation data changes at different times, but most should show the changes in the next day or two, if they aren't already.

Finally, if you're a time traveler who has discovered this thread because Google thinks your IP address is in the wrong country, I'll roll up the helpful information already provided by community members:
* If you go to http://www.google.com/ncr, that will never redirect based on geolocation, so that can be used as a temporary workaround. * Please report the bug to Google, as explained in this help article in the section "reporting incorrect IP detection".

@lucas:

Hi, I'm a Linode customer and a Google employee. Several of Linode's blocks of IP addresses were definitely getting bogus geolocation results. Thanks to some help from Linode's support folks, I got all the blocks that had bogus entries reported internally at Google, and everything should be fixed.

Confirmed: 97.107.134.213 is no longer in South Africa. Uitstekende werk. Dankie! -rt