Skip to main content

AS24262

HIcom

HAMANASU INFORMATION Co., Ltd.

Registry

Authoritative registration data

AS number
24262
Name
HIcom
Organisation
HAMANASU INFORMATION Co., Ltd.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS24262
202.122.136.0/21 IPv4 /21 not checked
2406:9b40::/32 IPv6 /32 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 AS24262
Address families
BBIX Tokyo 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 AS24262 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS24262 in AS paths

Observed upstreams
Families
AS17676 GIGAINFRA 347 628
v4 v6
AS24482 SGGS-AS-AP 2 23
v4 v6
AS9002 RETN-AS 2 4
v4 v6
AS4713 OCN 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS24262 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS2500 WIDE-BB 1 2
v4 v6
AS18106 VIEWQWEST-SG-AP 1 2
v4 v6
AS49544 i3Dnet 1 2
v4 v6
AS59105 HOMENOC 1 2
v4 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.