Skip to main content

AS151385

JAPANET-H

Japanet Holdings Co.,Ltd.

Registry

Authoritative registration data

AS number
151385
Name
JAPANET-H
Organisation
Japanet Holdings Co.,Ltd.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS151385
157.66.22.0/23 IPv4 /23 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 AS151385
Address families
BBIX Osaka 10,000 Mbps IPv4 · IPv6
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 AS151385 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS151385 in AS paths

Observed upstreams
Families
AS2519 VECTANT 148 184
v4
AS17676 GIGAINFRA 81 103
v4
AS6939 HURRICANE 23 25
v4
AS9002 RETN-AS 2 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS151385 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 9
v4
AS2500 WIDE-BB 1 1
v4
AS18106 VIEWQWEST-SG-AP 1 1
v4
AS35280 F5 1 1
v4
AS49544 i3Dnet 1 1
v4
AS59105 HOMENOC 1 1
v4

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.