asn.dev

Observed topology

AS32489 AMANAHA-NEW

Hosting ARIN

Upstreams 9 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 10
Adjacent (IPv6) 11
Upstream graph Who carries AS32489, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS32489 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32489: 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
AS6461Zayo BandwidthTransitIPv4 IPv61,752
AS174Cogent Communications, LLCTransitIPv4 IPv61,058
AS6939Hurricane Electric LLCTransitIPv4 IPv6356
AS36236NetActuate, IncHostingIPv4 IPv6120
AS22652Videotron LteeResidentialIPv4 IPv681
AS24482SG.GSHostingIPv4 IPv643
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv643
AS1403EBOXResidentialIPv616
AS20473The Constant Company, LLCHostingIPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS32001Hypha Worker Co-operative Inc.UnclassifiedIPv4 IPv6182
AS399542Flying Goose SystemsUnclassifiedIPv4 IPv6144
AS53363TANGRAM CANADA INC.UnclassifiedIPv458

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4 IPv61,987
AS174Cogent Communications, LLCTransitIPv4 IPv61,182
AS6939Hurricane Electric LLCTransitIPv4 IPv6356
AS32001Hypha Worker Co-operative Inc.UnclassifiedIPv4 IPv6182
AS399542Flying Goose SystemsUnclassifiedIPv4 IPv6144
AS36236NetActuate, IncHostingIPv4 IPv6138
AS22652Videotron LteeResidentialIPv4 IPv688
AS53363TANGRAM CANADA INC.UnclassifiedIPv458
AS24482SG.GSHostingIPv4 IPv643
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv643

All 12 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M 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.