Question

IP location


Badge
  • First activity
  • 0 replies

I’m located in Maryland using Tmobile as my ISP. The IP address that is assigned to me is in The Bronx, NY, so my search engine results always come back with NY and NJ results. Is there a way to change this?


3 replies

Userlevel 6
Badge +14

I don’t see a way to change the IP address in the settings. I have had this same issue and this could be related to the browser settings. It commonly happened with Google for me. Check your Site Settings for Google and see if that works. Also, try clearing your browser history for the one you’re using and search again go see if that helps.

Userlevel 4
Badge +3

Screwy 464 “tunnel” they use… coupled with bad geodata.  The public facing v4 address where you “exit” isn’t necessarily yours alone--could easily be shared with others, like with Carrier Grade NAT and such.

I am in Florence, SC… reports me as Charlotte, NC.

Doesn’t appear to be isolated to the v4 address either.  The IPv6 address handed out to my modem resolves as a Charlotte location as well.  So even if we were able to do a proper v6 delegation/passthrough, the geodata would likely still be off-kilter.

Userlevel 4
Badge +3

yeah.. out of curiosity, I set up v6 passthrough just to see if it changed.  Phone’s browser uses v6 lookups and such (on the windoze laptop, the browsers fall back to v4 dns lookups because of the 300ms “race” thing it does).

Phone still reports geolocation as Charlotte when I hit websites.  One I often use (myip.ms) shows the v6 address and all--but still says I am in Charlotte.

And this is what shows up starting at the third hop (after my modem’s v6 assigned address) when I try to trace directly to google’s v6 dns (2001:4860:4860::8888):

 

3   307 ms    39 ms    53 ms  2607:fb90:5331:aef9:0:1e:8445:ab40
4     *        *        *     Request timed out.
5     *        *        *     Request timed out.
6     *        *        *     Request timed out.
7   223 ms    36 ms    38 ms  2001:438:fffe::1022
8    77 ms    37 ms    38 ms  2001:4860:1:1:0:3e:0:2
9    60 ms   229 ms    56 ms  2001:4860:0:1165::1
10    62 ms    60 ms    57 ms  2001:4860:0:1::135
11   369 ms    56 ms    55 ms  dns.google [2001:4860:4860::8888]

 

Note that first hop with the >300ms response (#3) resolves as a TMO hop assigned to Charlotte.

It then gets handed off to Zayo (a peer typically seen going through the northern/central/midwest regions, not the southern paths typically sent through CenturyLink/Level3 via Atlanta from here)

 

Basically… there are a LOT of issues they need to deal with in their infrastructure and peering.

Was not really ready for primetime/mainstream use as a home ISP yet.. a lot of snafus like this.

Reply