Observed topology
AS852 TELUS Communications
Residential ARIN
Transit
Upstream networks
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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 10,070 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 7,014 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 6,326 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 5,801 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 4,528 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 1,412 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 1,388 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 961 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 677 |
| AS11164 | Internet2 | Education | IPv4 | 675 |
Transit
Downstream networks
Networks for which AS852 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 6,831 |
| AS6327 | Shaw Communications | Residential | IPv4 IPv6 | 4,000 |
| AS7029 | Windstream Communications LLC | Residential | IPv4 IPv6 | 3,152 |
| AS808 | GONET | Unclassified | IPv4 | 3,079 |
| AS16696 | iTel Networks Inc | Unclassified | IPv4 | 2,558 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 2,454 |
| AS4766 | Korea Telecom | Mobile | IPv4 IPv6 | 2,178 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,074 |
| AS7861 | TELUS Communications Inc. | Unclassified | IPv4 | 1,970 |
| AS11489 | Bell Canada | Unclassified | IPv4 | 1,864 |
Adjacency
Adjacent networks
Every AS seen directly next to AS852 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 308,336 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 215,987 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 163,043 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 155,779 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 122,906 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 122,010 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 93,778 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 63,063 |
| AS7922 | Comcast Cable Communications, LLC | Residential | IPv4 IPv6 | 11,901 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 9,713 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.