asn.dev

Observed topology

AS20340 CALLTOWER - CallTower, Inc.

Hosting ARIN Content

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS20340: 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 LLCTransitIPv4622
AS8220COLT Technology Services Group LimitedHostingIPv4136
AS16260EMEA Ltd.UnclassifiedIPv475
AS174Cogent Communications, LLCTransitIPv473
AS19855Masergy Communications, Inc.UnclassifiedIPv458
AS3356Level 3 Parent, LLCTransitIPv448
AS7018AT&T Enterprises, LLCResidentialIPv446
AS3257GTT Communications Inc.TransitIPv438
AS13768Aptum TechnologiesHostingIPv436
AS24482SG.GSHostingIPv414

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS46168CallTower, Inc.UnclassifiedIPv459

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4622
AS8220COLT Technology Services Group LimitedHostingIPv4136
AS3257GTT Communications Inc.TransitIPv497
AS16260EMEA Ltd.UnclassifiedIPv475
AS174Cogent Communications, LLCTransitIPv473
AS46168CallTower, Inc.UnclassifiedIPv459
AS19855Masergy Communications, Inc.UnclassifiedIPv458
AS3356Level 3 Parent, LLCTransitIPv448
AS7018AT&T Enterprises, LLCResidentialIPv446
AS13768Aptum TechnologiesHostingIPv436

Provenance

Where this comes from

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