Observed topology
AS5769 VIDEOTRON - Videotron Ltee
Residential ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS5769: 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 | 4,076 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,801 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,355 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,435 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,388 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 522 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 511 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 322 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 263 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 260 |
Transit
Downstream networks
Networks for which AS5769 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS54198 | Videotron Ltee | Unclassified | IPv4 | 1,463 |
| AS20365 | Videotron Ltee | Mobile | IPv4 IPv6 | 1,242 |
| AS395761 | Videotron Ltee | Unclassified | IPv4 | 1,140 |
| AS395592 | Ericsson Inc. | Unclassified | IPv4 IPv6 | 198 |
| AS398959 | Energir L.P. | Unclassified | IPv4 | 115 |
| AS397617 | UNNO | Unclassified | IPv4 | 94 |
| AS30236 | Cronomagic Canada Inc. | Unclassified | IPv4 | 87 |
| AS400486 | Argo Innovation Labs Inc. | Unclassified | IPv4 | 58 |
| AS1824 | Vertisoft | Hosting | IPv4 | 57 |
| AS398833 | Bombardier Inc. | Unclassified | IPv4 | 48 |
Adjacency
Adjacent networks
Every AS seen directly next to AS5769 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 6,166 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,508 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,865 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 1,821 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,659 |
| AS54198 | Videotron Ltee | Unclassified | IPv4 | 1,463 |
| AS20365 | Videotron Ltee | Mobile | IPv4 IPv6 | 1,242 |
| AS395761 | Videotron Ltee | Unclassified | IPv4 | 1,140 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 655 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 634 |
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.