asn.dev

Observed topology

AS55943 ONATI-AS-AP - ONATI

Unclassified APNIC Cable/DSL/ISP

Upstreams 2 carry this network
Downstreams 5 this network carries
Adjacent (IPv4) 8
Adjacent (IPv6) 4
Upstream graph Who carries AS55943, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS55943 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55943: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv6307
AS6939Hurricane Electric LLCTransitIPv662

Transit

Downstream networks

inferred

Networks for which AS55943 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS9471ONATIResidentialIPv4 IPv612,738
AS138179PACIFIC MOBILE TELECOMMobileIPv4 IPv6751
AS55885No. 1 Commercial CenterUnclassifiedIPv4300
AS10131Telecom Cook IslandsResidentialIPv4197
AS14789Cloudflare, Inc.UnclassifiedIPv42

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS55943 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS9471ONATIResidentialIPv4 IPv612,738
AS3257GTT Communications Inc.TransitIPv4 IPv611,304
AS6939Hurricane Electric LLCTransitIPv4 IPv62,702
AS138179PACIFIC MOBILE TELECOMMobileIPv4 IPv6751
AS36149Hawaiian Telcom Services Company, Inc.ResidentialIPv4365
AS55885No. 1 Commercial CenterUnclassifiedIPv4300
AS10131Telecom Cook IslandsResidentialIPv4197
AS14789Cloudflare, Inc.UnclassifiedIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.