Observed topology
AS16696 ITELNETWORKS - iTel Networks Inc
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS16696: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,268 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 | 2,585 |
| AS6327 | Shaw Communications | Residential | IPv4 | 690 |
| AS577 | Bell Canada | Mobile | IPv4 | 426 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 193 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 190 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 114 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 98 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 98 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 93 |
Transit
Downstream networks
Networks for which AS16696 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS53661 | PPI | Unclassified | IPv4 | 695 |
| AS399063 | Rural Net | Unclassified | IPv4 | 592 |
| AS46915 | Lyttonnet | Unclassified | IPv4 | 326 |
| AS14118 | FortisBC Inc. | Unclassified | IPv4 | 132 |
| AS399376 | Liquor Control Board of Ontario | Unclassified | IPv4 | 132 |
| AS397136 | F12.net Inc. | Unclassified | IPv4 | 66 |
| AS40751 | -Reserved AS- | Unclassified | IPv4 | 59 |
| AS396294 | Converging Technology Solutions Inc. | Unclassified | IPv4 | 59 |
| AS22790 | SCADACore Inc. | Unclassified | IPv4 | 58 |
| AS16920 | Wind River Systems, Inc. | Unclassified | IPv4 | 57 |
Adjacency
Adjacent networks
Every AS seen directly next to AS16696 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,568 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 | 3,089 |
| AS6327 | Shaw Communications | Residential | IPv4 | 946 |
| AS53661 | PPI | Unclassified | IPv4 | 695 |
| AS399063 | Rural Net | Unclassified | IPv4 | 592 |
| AS577 | Bell Canada | Mobile | IPv4 | 505 |
| AS46915 | Lyttonnet | Unclassified | IPv4 | 326 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 211 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 208 |
| AS14118 | FortisBC Inc. | Unclassified | IPv4 | 132 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.