asn.dev

Observed topology

AS109 CISCOSYSTEMS

Unclassified ARIN Enterprise

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS109: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,124
AS6939Hurricane Electric LLCTransitIPv4 IPv61,787
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6459
AS9498BHARTI Airtel Ltd.MobileIPv4407
AS4637Telstra GlobalUnclassifiedIPv4 IPv6400
AS1221Telstra LimitedMobileIPv4 IPv6263
AS701Verizon BusinessResidentialIPv4 IPv6245
AS4812China Telecom (Group)ResidentialIPv4238
AS1299Arelion Sweden ABTransitIPv4 IPv6234
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6210

All 18 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,124
AS6939Hurricane Electric LLCTransitIPv4 IPv61,787
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6459
AS9498BHARTI Airtel Ltd.MobileIPv4407
AS4637Telstra GlobalUnclassifiedIPv4 IPv6400
AS1221Telstra LimitedMobileIPv4 IPv6263
AS701Verizon BusinessResidentialIPv4 IPv6245
AS4812China Telecom (Group)ResidentialIPv4238
AS1299Arelion Sweden ABTransitIPv4 IPv6234
AS4755TATA Communications formerly VSNL is Leading ISPHostingIPv4 IPv6210

All 18 adjacent →

Provenance

Where this comes from

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