Location of IP Address

Hi! I just started with a new Debian server out of Singapore. I noticed the default time zone was EST so I changed it to match where the server is located. That seems to be okay. However when I run a search for my server's IP address on https://www.iplocation.net/ it shows that it is in NJ for all but one geoip site. That lone one shows it as a Canadian IP. Why doesn't my IP register as being located in Singapore since that is where the server is located?


  • I've just tested one of my Netherlands IP.

    It appears that website queries the IP against several ip2location databases (like maxmind and others). For all databases except the first one (ip2location DB6) it shows my ip correctly in the Netherlands. But on that first one, it also shows as a New Jersey.

    I'm pretty sure that's because Vultr is a New Jersey company and that specific database happens to tell you the location of the entity that actually owns that IP space and not the place where the final server that has that IP assigned is.
  • edited February 2017
    Hey @PresidentShinra

    Sometimes it can take quite awhile - I've seen it take a week or two for database queries to reflect the location.
  • Interesting. It has been almost two months and the IP address still shows a US based IP instead of Singapore.
  • I have the same problem,my server location is in japan,but ip address is in canada.hope can fix it ASAP
  • These databases are not technically linked to location of an IP - they are just reverse compiled using various techniques (in the case of Uk residential DSL lines, generally hopelessy unreliable due to the fact many telcos use a seperate national internal network, so just about all users from anywhere hit "the internet" in London, and without regional IP mapping you can be show as being from anywhere in the UK, depending on the database!)

    So, a database entry can be - and often is - wrong.

    This is not a techincal problem assuming all the routing is correct - it's certainly not a problem of Vultr's.

    You wanna see BGP announce routes, but the easiest way to actually trace your IPs location is simply use the 'traceroute' command. For a network which is IP all the way (like what your server will have), the traceroute should pop right through some local japanese routers.

    00:57 (13) "/tmp" jamie@lapcat% traceroute hnd-jp-ping.vultr.com
    traceroute to hnd-jp-ping.vultr.com (, 64 hops max, 40 byte packets
    1 [AS0] router.home.dyslexicfish.net ( 1.956 ms 3.192 ms 2.218 ms
    2 * * *
    3 [AS26415] host-78-151-229-229.as13285.net ( 26.466 ms 9.945 ms 11.117 ms
    4 [AS26415] host-78-151-229-232.as13285.net ( 9.719 ms 9.916 ms
    [AS26415] host-78-151-229-228.as13285.net ( 10.694 ms
    5 [AS26415] host-78-144-9-197.as13285.net ( 18.538 ms
    [AS26415] host-78-144-9-205.as13285.net ( 15.009 ms 15.308 ms
    6 [AS2914] ( 17.770 ms 18.148 ms 17.411 ms
    7 [AS2914] ae-13.r24.londen12.uk.bb.gin.ntt.net ( 17.664 ms 16.810 ms 16.437 ms
    8 [AS2914] ae-5.r24.nycmny01.us.bb.gin.ntt.net ( 88.170 ms 81.999 ms 80.717 ms
    9 [AS2914] ae-4.r22.sttlwa01.us.bb.gin.ntt.net ( 159.938 ms 153.348 ms 173.930 ms
    10 [AS2914] ae-13.r30.tokyjp05.jp.bb.gin.ntt.net ( 238.680 ms 237.586 ms 232.442 ms
    11 [AS2914] ae-2.r02.tokyjp05.jp.bb.gin.ntt.net ( 237.932 ms 240.511 ms 234.465 ms
    12 [AS2914] ce-0-14-0-1.r02.tokyjp05.jp.ce.gin.ntt.net ( 252.226 ms 249.903 ms 260.736 ms
    13 * * *
    14 [AS20473] vl516-ds1-b5-r2605.tyo1.choopa.net ( 269.484 ms 239.437 ms 247.503 ms
    15 * * *
    16 [AS20473] ( 243.175 ms 240.991 ms 237.770 ms
Sign In or Register to comment.