Skip to main content

AS17707

DATAHOTEL-JP

AS for DATAHOTEL, which is one of iDC in Japan,

Registry

Authoritative registration data

AS number
17707
Name
DATAHOTEL-JP
Organisation
AS for DATAHOTEL, which is one of iDC in Japan,
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

23

IPv6 prefixes

4

Total announced

27

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS17707
125.6.128.0/17 IPv4 /17 not checked
125.6.128.0/18 IPv4 /18 not checked
203.104.192.0/18 IPv4 /18 not checked
125.6.0.0/19 IPv4 /19 not checked
125.6.192.0/19 IPv4 /19 not checked
125.6.112.0/20 IPv4 /20 not checked
202.5.64.0/20 IPv4 /20 not checked
203.104.96.0/20 IPv4 /20 not checked
203.131.192.0/20 IPv4 /20 not checked
203.174.64.0/20 IPv4 /20 not checked
218.223.16.0/20 IPv4 /20 not checked
219.109.208.0/20 IPv4 /20 not checked
61.121.208.0/20 IPv4 /20 not checked
125.6.252.0/22 IPv4 /22 not checked
125.6.112.0/23 IPv4 /23 not checked
125.6.180.0/23 IPv4 /23 not checked
125.6.175.0/24 IPv4 /24 not checked
125.6.184.0/24 IPv4 /24 not checked
125.6.189.0/24 IPv4 /24 not checked
203.104.209.0/24 IPv4 /24 not checked
203.174.64.0/24 IPv4 /24 not checked
203.174.66.0/24 IPv4 /24 not checked
27.133.224.0/24 IPv4 /24 not checked
2407:3000::/32 IPv6 /32 not checked
2407:3000:6::/48 IPv6 /48 not checked
2407:3000:6a::/48 IPv6 /48 not checked
2407:3000:6d::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS17707
Address families
BBIX Tokyo 100,000 Mbps IPv4 · IPv6
JPNAP Tokyo: Peering 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS17707 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS17707 in AS paths

Observed upstreams
Families
AS2497 IIJ 277 3,951
v4 v6
AS2516 KDDI 438 2,600
v4 v6
AS2519 VECTANT 534 1,715
v4 v6
AS6939 HURRICANE 24 421
v4
AS8966 Etisalat-AS 3 49
v4
AS4713 3 35
v4 v6
AS9304 HUTCHISON-AS-AP 1 17
v4
AS137409 GSLNETWORKS-AS-AP 1 17
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS17707 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

10 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 188
v4 v6
AS2500 WIDE-BB 1 18
v4 v6
AS9002 RETN-AS 1 18
v4 v6
AS17639 CONVERGE-AS 1 18
v4 v6
AS45489 SLT-GLOBAL 1 18
v4 v6
AS49544 i3Dnet 1 18
v4 v6
AS18106 VIEWQWEST-SG-AP 1 17
v4
AS59105 1 17
v4
AS25152 K-ROOT-SERVER 1 1
v6
AS35280 F5 1 1
v6

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.