Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › IP location
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

IP location

sktanmoysktanmoy Member
in Help

Can you guys help me to understand the location of this IP(204.44.122.16)? Provider is saying it's Dallas. But all geo database is telling it as LA.

Comments

  • 0xdragon0xdragon Member
    edited September 2014

    Yes, it's in Dallas, the ASN points to LA, but the traceroute goes to Dallas.

    United States Los Angeles Quadranet Inc
ASN     United States AS29761 AS-QUADRANET - QuadraNet, Inc,US (registered May 01, 2003)
  • ChuckChuck Member
    edited September 2014

    Who is the provider?

  • IshaqIshaq Member
    edited September 2014

    It is in Dallas:

    11 165 ms 148 ms 141 ms dal-ten2-1-nsh-ten1-4.bboi.net [64.127.130.50]

    12 142 ms 141 ms 141 ms 8011-on-net-cust.bboi.net [64.127.129.118]

    QuadraNet have a Dallas location too. IPs may be SWIPed to LA as that's their flagship location.

  • DalekOfSkaroDalekOfSkaro Member

    No, they are not lying. GeoLocation often goes by ASN Path. And since QuadraNet's ASN origin is LA, GeoLocation will report LA.

    $ traceroute 204.44.122.16
traceroute to 204.44.122.16 (204.44.122.16), 64 hops max, 52 byte packets
 1   (192.168.1.1)  1.197 ms  1.042 ms  0.919 ms
 2  10.4.128.1 (10.4.128.1)  11.855 ms  10.124 ms  11.936 ms
 3  ip72-214-194-57.ga.at.cox.net (72.214.194.57)  10.321 ms  8.881 ms  10.544 ms
 4  maribprj01-ae1.0.rd.at.cox.net (68.1.0.41)  23.614 ms  24.847 ms  23.427 ms
 5  telx.10ge.atl.bboi.net (198.32.132.12)  25.401 ms  24.025 ms  24.856 ms
 6  nsh-ten1-1-atl-ten3-2.bboi.net (64.127.130.58)  30.134 ms  31.146 ms  32.686 ms
 7  dal-ten2-1-nsh-ten1-4.bboi.net (64.127.130.50)  40.659 ms  38.926 ms  40.598 ms
 8  8011-on-net-cust.bboi.net (64.127.129.118)  44.550 ms  48.939 ms  46.456 ms
 9  204.44.122.2.static.quadranet.com (204.44.122.2)  46.985 ms  44.286 ms  44.584 ms
10  204.44.122.16.static.quadranet.com (204.44.122.16)  43.370 ms  45.373 ms  47.437 ms

$ ping 204.44.122.16
PING 204.44.122.16 (204.44.122.16): 56 data bytes
64 bytes from 204.44.122.16: icmp_seq=0 ttl=54 time=46.784 ms
64 bytes from 204.44.122.16: icmp_seq=1 ttl=54 time=46.477 ms
64 bytes from 204.44.122.16: icmp_seq=2 ttl=54 time=46.675 ms

    I'm on the East Coast, and this traceroute and ping can't be hitting LA, this is indeed Dallas.

  • mokafumokafu Member

    I'm seeing a 1ms ping from Incero in Dallas, so It's indeed in Dallas.

  • DalekOfSkaroDalekOfSkaro Member

    Bingo :-)

  • jnguyenjnguyen Member
    edited September 2014

    Number one 1 pet peeve

    I hate explaining geolocation and will get mad posted if you argue against tracert logic

  • sktanmoysktanmoy Member

    Provider is WeLoveServer. Not sure what is going on! I failed to understand the Traceroute report :(

  • IshaqIshaq Member

    Ishaq said: QuadraNet have a Dallas location too. IPs may be SWIPed to LA as that's their flagship location.

    Isn't that clear enough?

    The hardware and network are in Dallas. IPs are just registered in LA because that's their flagship location.

  • DalekOfSkaroDalekOfSkaro Member

    sktanmoy said: Provider is WeLoveServer. Not sure what is going on! I failed to understand the Traceroute report :(

    If your hosting provider fails to understand a traceroute output,

  • IshaqIshaq Member

    DalekOfSkaro said: If your hosting provider fails to understand a traceroute output,

    Re-read it, he said he doesn't understand the traceroute.

Sign In or Register to comment.