Skip to main content

AS55382

HOT-CHA

Nagato city office

Registry

Authoritative registration data

AS number
55382
Name
HOT-CHA
Organisation
Nagato city office
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 AS55382
223.223.160.0/22 IPv4 /22 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 AS55382
Address families
JPIX 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 AS55382 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS55382 in AS paths

Observed upstreams
Families
AS2519 VECTANT 221 270
v4
AS6939 HURRICANE 30 35
v4
AS7670 CTNET 9 12
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS55382 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 9
v4
AS1828 UNITAS 1 1
v4
AS4777 APNIC-COLO 1 1
v4
AS35280 F5 1 1
v4
AS36236 NETACTUATE 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.