Howdy, Stranger!

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


Linode Tokyo 2 IP ranges
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.

Linode Tokyo 2 IP ranges

rm_rm_ IPv6 Advocate, Veteran
edited August 2017 in General

Created a few Linode Japan boxes, and all of them got IPs from this range:

NetRange:       172.104.0.0 - 172.105.255.255
CIDR:           172.104.0.0/15
NetName:        LINODE-US
NetHandle:      NET-172-104-0-0-1
Parent:         NET172 (NET-172-0-0-0-0)
NetType:        Direct Allocation
OriginAS:       AS3595, AS63949, AS21844, AS6939, AS8001
Organization:   Linode (LINOD)
RegDate:        2015-06-19
Updated:        2016-12-29
Comment:        Linode, LLC 
Comment:        http://www.linode.com
Ref:            https://whois.arin.net/rest/net/NET-172-104-0-0-1

OrgName:        Linode
OrgId:          LINOD
Address:        329 E. Jimmie Leeds Road
Address:        Suite A
City:           Galloway
StateProv:      NJ
PostalCode:     08205
Country:        US
RegDate:        2008-04-24
Updated:        2017-01-28
Comment:        http://www.linode.com
Ref:            https://whois.arin.net/rest/org/LINOD

OrgNOCHandle: LNO21-ARIN
OrgNOCName:   Linode Network Operations
OrgNOCPhone:  +1-609-380-7304 
OrgNOCEmail:  [email protected]
OrgNOCRef:    https://whois.arin.net/rest/poc/LNO21-ARIN

OrgTechHandle: LNO21-ARIN
OrgTechName:   Linode Network Operations
OrgTechPhone:  +1-609-380-7304 
OrgTechEmail:  [email protected]
OrgTechRef:    https://whois.arin.net/rest/poc/LNO21-ARIN

OrgAbuseHandle: LAS12-ARIN
OrgAbuseName:   Linode Abuse Support
OrgAbusePhone:  +1-609-380-7100 
OrgAbuseEmail:  [email protected]
OrgAbuseRef:    https://whois.arin.net/rest/poc/LAS12-ARIN
$ geoiplookup 172.104.102.35
GeoIP Country Edition: IP Address not found

Is this the only range they assign currently, or anyone had luck getting APNIC (and properly geolocated) IPs there? And when or how often?

Comments

  • AnthonySmithAnthonySmith Member, Patron Provider

    I contacted them after you berated the JP LES service for using an ARIN IP suggesting Linode at least assign APNIC IP's

    Linode was quite clear that they are only assigning from ARIN now in Japan unless you just happen to pick up a reallocated APNIC batch at random points in the year.

    In an ironic twist, I now have 1 x APNIC with vultr, I believe Oliver (RansomIT) is setting up a pop in Japan in the next few months, that will then become the best option I expect.

  • rm_rm_ IPv6 Advocate, Veteran
    edited August 2017

    Yeah I remember with Vultr it was close to 50/50 chance to get ARIN or APNIC (maybe worse by now). That's why I wondered how it is with Linode. So far 5 created Linodes all had ARIN.

  • rm_ said: Is this the only range they assign currently, or anyone had luck getting APNIC (and properly geolocated) IPs there? And when or how often?

    I create 2 for testing, both have different IP

    1st : 139.162.107.103
    2nd : 172.104.72.156

    Thanked by 1rm_
  • rm_rm_ IPv6 Advocate, Veteran
    edited August 2017

    Hm, these are also routed differently. Tried from 3 different locations, the 139.162.107.x network has a lower ping, by as much as 50-60ms.

  • rm_rm_ IPv6 Advocate, Veteran
    edited August 2017

    Well this is silly, ping for neighbour IPs even in the same /24 varies by this much too.

  • The range is properly geolocated - it's just your GeoIP database that isn't up to date.

    If I query the maxmind database:

    {
      "ip": "172.104.102.35",
      "iso_code": "JP",
      "country": "Japan",
      "city": "Tokyo",
      "state": "13",
      "state_name": "Tokyo",
      "postal_code": "100-0001",
      "lat": 35.6427,
      "lon": 139.7677,
      "timezone": "Asia/Tokyo",
      "continent": "AS",
      "currency": "JPY",
      "default": false
    }
    

    Aaand I haven't updated my database since beginning of June.

    Thanked by 1Clouvider
  • rm_rm_ IPv6 Advocate, Veteran
    edited August 2017

    Zerpy said: The range is properly geolocated

    Sure I checked the maxmind website and it is, but the point is, not everyone uses that for geolocation checking, some sites/services will simply use data from IP whois, and that it only says NJ/US in the whois, is a huge oversight and demonstrates that they don't care much.

    Compare to the ARIN whois of Vultr:

    NetRange:       108.61.200.0 - 108.61.201.255
    CIDR:           108.61.200.0/23
    NetName:        NET-108-61-200-0-23
    NetHandle:      NET-108-61-200-0-1
    Parent:         CHOOPA-NETBLK08 (NET-108-61-0-0-1)
    NetType:        Reassigned
    OriginAS:       
    Organization:   Vultr Holdings, LLC (VHL-45)
    RegDate:        2015-03-05
    Updated:        2015-03-05
    Ref:            https://whois.arin.net/rest/net/NET-108-61-200-0-1
    
    
    ===> OrgName:        Vultr Holdings, LLC
    ===> OrgId:          VHL-45
    ===> Address:        TRC Bldg., C-tower, B-block, 4F
    ===> Address:        6-5-2
    ===> City:           Heiwajima
    ===> StateProv:      
    ===> PostalCode:     143-0006
    ===> Country:        JP
    ===> RegDate:        2015-03-05
    ===> Updated:        2015-03-05
    ===> Ref:            https://whois.arin.net/rest/org/VHL-45
    
    
    OrgTechHandle: VULTR-ARIN
    OrgTechName:   Vultr Abuse
    OrgTechPhone:  +1-973-849-0500 
    OrgTechEmail:  [email protected]
    OrgTechRef:    https://whois.arin.net/rest/poc/VULTR-ARIN
    
    OrgAbuseHandle: VULTR-ARIN
    OrgAbuseName:   Vultr Abuse
    OrgAbusePhone:  +1-973-849-0500 
    OrgAbuseEmail:  [email protected]
    OrgAbuseRef:    https://whois.arin.net/rest/poc/VULTR-ARIN
    
    # end
    
    
    # start
    
    NetRange:       108.61.0.0 - 108.61.255.255
    CIDR:           108.61.0.0/16
    NetName:        CHOOPA-NETBLK08
    NetHandle:      NET-108-61-0-0-1
    Parent:         NET108 (NET-108-0-0-0-0)
    NetType:        Direct Allocation
    OriginAS:       AS20473
    Organization:   Choopa, LLC (CHOOP-1)
    RegDate:        2010-12-08
    Updated:        2012-03-02
    Ref:            https://whois.arin.net/rest/net/NET-108-61-0-0-1
    
    
    OrgName:        Choopa, LLC
    OrgId:          CHOOP-1
    Address:        14 Cliffwood Ave Suite 300
    City:           Matawan
    StateProv:      NJ
    PostalCode:     07747
    Country:        US
    RegDate:        2006-10-03
    Updated:        2016-01-11
    Comment:        http://www.choopa.net/
    Ref:            https://whois.arin.net/rest/org/CHOOP-1
    
    
    OrgAbuseHandle: ABUSE1143-ARIN
    OrgAbuseName:   Abuse Department
    OrgAbusePhone:  +1-973-849-0500 
    OrgAbuseEmail:  [email protected]
    OrgAbuseRef:    https://whois.arin.net/rest/poc/ABUSE1143-ARIN
    
    OrgNOCHandle: NETWO1159-ARIN
    OrgNOCName:   Network Operations
    OrgNOCPhone:  +1-973-849-0500 
    OrgNOCEmail:  [email protected]
    OrgNOCRef:    https://whois.arin.net/rest/poc/NETWO1159-ARIN
    
    OrgTechHandle: NETWO1159-ARIN
    OrgTechName:   Network Operations
    OrgTechPhone:  +1-973-849-0500 
    OrgTechEmail:  [email protected]
    OrgTechRef:    https://whois.arin.net/rest/poc/NETWO1159-ARIN
    
    RAbuseHandle: ABUSE1143-ARIN
    RAbuseName:   Abuse Department
    RAbusePhone:  +1-973-849-0500 
    RAbuseEmail:  [email protected]
    RAbuseRef:    https://whois.arin.net/rest/poc/ABUSE1143-ARIN
    
    RNOCHandle: NETWO1159-ARIN
    RNOCName:   Network Operations
    RNOCPhone:  +1-973-849-0500 
    RNOCEmail:  [email protected]
    RNOCRef:    https://whois.arin.net/rest/poc/NETWO1159-ARIN
    
    RTechHandle: NETWO1159-ARIN
    RTechName:   Network Operations
    RTechPhone:  +1-973-849-0500 
    RTechEmail:  [email protected]
    RTechRef:    https://whois.arin.net/rest/poc/NETWO1159-ARIN
  • This that case - contact Linode, ask them to update the data in whois :-)

  • APNIC is empty, APNIC is hard to move space to, thus you buy ARIN (or even RIPE legacy) and use that. APNIC legacy for some reason also costs more.

    As you'll end by 2018 behind a Linode ASN anyway (no more Telehouse and similar) the geo point of the actual IP becomes even more moot.

Sign In or Register to comment.