asn.dev

Observed topology

AS32709 1-JOINK

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS32709: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6249
AS174Cogent Communications, LLCTransitIPv429
AS2914NTT America, Inc.TransitIPv4 IPv617
AS24482SG.GSHostingIPv44
AS14016Capcon NetworksUnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS46925PAVLOV MEDIA INCUnclassifiedIPv466
AS397150Union Hospital, Inc.UnclassifiedIPv459
AS398451Rose-Hulman Institute of Technology, IncUnclassifiedIPv4 IPv630
AS399315Indiana State UniversityUnclassifiedIPv412
AS396947Saint Mary of the Woods CollegeUnclassifiedIPv44
AS20203First Financial Bank NAUnclassifiedIPv42

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6387
AS46925PAVLOV MEDIA INCUnclassifiedIPv466
AS397150Union Hospital, Inc.UnclassifiedIPv459
AS174Cogent Communications, LLCTransitIPv441
AS2914NTT America, Inc.TransitIPv4 IPv638
AS398451Rose-Hulman Institute of Technology, IncUnclassifiedIPv4 IPv630
AS399315Indiana State UniversityUnclassifiedIPv412
AS24482SG.GSHostingIPv45
AS396947Saint Mary of the Woods CollegeUnclassifiedIPv44
AS14016Capcon NetworksUnclassifiedIPv42

Provenance

Where this comes from

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