asn.dev

Observed topology

AS16909 IMPUT

Unclassified ARIN NSP

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS16909: 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 IPv6218
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv6208
AS214481Wojciech CzapkowiczHostingIPv4 IPv650
AS24482SG.GSHostingIPv4 IPv610
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv67
AS34927iFog GmbHHostingIPv4 IPv65
AS9002RETN LimitedUnclassifiedIPv44
AS1103SURF B.V.UnclassifiedIPv4 IPv63
AS3130RGnet OUUnclassifiedIPv43
AS7575Australian Academic and Research Network AARNetEducationIPv43

All 15 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS396968imputUnclassifiedIPv6107
AS401507imputUnclassifiedIPv637

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6344
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv6212
AS396968imputUnclassifiedIPv6107
AS214481Wojciech CzapkowiczHostingIPv4 IPv653
AS401507imputUnclassifiedIPv637
AS24482SG.GSHostingIPv4 IPv614
AS394256Tech Futures Interactive Inc.UnclassifiedIPv4 IPv69
AS34927iFog GmbHHostingIPv4 IPv67
AS1103SURF B.V.UnclassifiedIPv4 IPv65
AS9002RETN LimitedUnclassifiedIPv44

All 17 adjacent →

Provenance

Where this comes from

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