Observed topology
AS20161 TRGO
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS20161: 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 |
|---|---|---|---|---|
| AS6327 | Shaw Communications | Residential | IPv4 IPv6 | 6,413 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,377 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 2,962 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 201 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 102 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 102 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 76 |
| AS1403 | EBOX | Residential | IPv6 | 6 |
| AS20473 | The Constant Company, LLC | Hosting | IPv6 | 3 |
| AS36236 | NetActuate, Inc | Hosting | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS20161 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29883 | Internet Hosting Servers | Hosting | IPv4 | 320 |
| AS912 | Hut 8 Mining Corp. | Unclassified | IPv4 | 182 |
| AS395741 | Tritech Financial Systems Inc. | Unclassified | IPv4 | 118 |
| AS22873 | Neighbourhood Connect | Unclassified | IPv4 | 59 |
| AS31790 | S&C Electric Canada Ltd. | Unclassified | IPv4 | 59 |
| AS47102 | Giesecke & Devrient Systems Canada, Inc. | Unclassified | IPv4 | 59 |
| AS203849 | Umicore NV | Unclassified | IPv4 | 14 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20161 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6327 | Shaw Communications | Residential | IPv4 IPv6 | 6,607 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,486 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 3,420 |
| AS29883 | Internet Hosting Servers | Hosting | IPv4 | 320 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 217 |
| AS912 | Hut 8 Mining Corp. | Unclassified | IPv4 | 182 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 119 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 119 |
| AS395741 | Tritech Financial Systems Inc. | Unclassified | IPv4 | 118 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 76 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.