Skip to main content

AS38639

HANABI

NTT DOCOMO BUSINESS, Inc.

Registry

Authoritative registration data

AS number
38639
Name
HANABI
Organisation
NTT DOCOMO BUSINESS, Inc.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

2

Total announced

7

Announced prefixes

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

Prefixes announced by AS38639
163.138.224.0/19 IPv4 /19 not checked
115.69.224.0/21 IPv4 /21 not checked
220.150.192.0/21 IPv4 /21 not checked
103.2.128.0/22 IPv4 /22 not checked
220.150.196.0/24 IPv4 /24 not checked
2402:c800::/32 IPv6 /32 not checked
2402:c800:cafe::/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 AS38639
Address families
JPNAP Tokyo: Peering 10,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 AS38639 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS38639 in AS paths

Observed upstreams
Families
AS2914 NTT-DATA-2914 248 1,321
v4 v6
AS4713 OCN 336 664
v4 v6
AS6939 HURRICANE 103 228
v4 v6
AS24482 SGGS-AS-AP 3 67
v4 v6
AS20485 TRANSTELECOM 7 19
v4
AS9002 RETN-AS 3 11
v4 v6
AS9370 SAKURA-B 1 5
v4 v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS38639 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS17639 CONVERGE-AS 2 6
v4 v6
AS25152 K-ROOT-SERVER 2 6
v4 v6
AS45489 SLT-GLOBAL 2 6
v4 v6
AS49544 i3Dnet 2 6
v4 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.