asn.dev

Observed topology

AS852 ASN852 - TELUS Communications Inc.

Residential ARIN NSP

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS852: 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
AS1299Arelion Sweden ABTransitIPv4 IPv610,196
AS2914NTT America, Inc.TransitIPv4 IPv66,814
AS6939Hurricane Electric LLCTransitIPv4 IPv66,041
AS174Cogent Communications, LLCTransitIPv4 IPv65,691
AS3257GTT Communications Inc.TransitIPv4 IPv63,869
AS1403EBOXResidentialIPv4 IPv61,418
AS22652Videotron LteeResidentialIPv4 IPv61,392
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv61,010
AS33891Core-Backbone GmbHHostingIPv4681
AS11164Internet2EducationIPv4678

All 16 upstreams →

Transit

Downstream networks

All 402

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

ASNetworkTypeFamiliesPaths seen
AS16509Amazon.com, Inc.HostingIPv4 IPv66,912
AS9498BHARTI Airtel Ltd.MobileIPv4 IPv65,051
AS6327Shaw CommunicationsResidentialIPv4 IPv64,004
AS7029Windstream Communications LLCResidentialIPv4 IPv63,132
AS808GONETUnclassifiedIPv42,993
AS16696iTel Networks IncUnclassifiedIPv42,671
AS13335Cloudflare, Inc.HostingIPv4 IPv62,523
AS4766Korea TelecomMobileIPv4 IPv62,176
AS7861TELUS Communications Inc.UnclassifiedIPv41,948
AS174Cogent Communications, LLCTransitIPv4 IPv61,829

All 402 downstreams →

Adjacency

Adjacent networks

All 402

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4 IPv6306,363
AS6939Hurricane Electric LLCTransitIPv4 IPv6220,627
AS2914NTT America, Inc.TransitIPv4 IPv6164,658
AS1299Arelion Sweden ABTransitIPv4 IPv6156,589
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6119,221
AS6461Zayo BandwidthTransitIPv4 IPv6119,193
AS174Cogent Communications, LLCTransitIPv4 IPv697,172
AS3320Deutsche Telekom AGMobileIPv4 IPv662,690
AS7922Comcast Cable Communications, LLCResidentialIPv4 IPv611,997
AS16509Amazon.com, Inc.HostingIPv4 IPv69,947

All 402 adjacent →

Provenance

Where this comes from

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