Observed topology
AS19122 ESTRUXTURE-ON-19122
Hosting ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS19122: 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 | 191 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 111 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 83 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 15 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 9 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS394256 | Tech Futures Interactive Inc. | Unclassified | IPv4 IPv6 | 9 |
| AS1403 | EBOX | Residential | IPv6 | 6 |
| AS20473 | The Constant Company, LLC | Hosting | IPv6 | 3 |
Transit
Downstream networks
Networks for which AS19122 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS18588 | Postmedia Network Inc | Hosting | IPv4 | 112 |
| AS54572 | Nasdaq, Inc. | Unclassified | IPv4 | 57 |
| AS27549 | Cloud at Work | Unclassified | IPv4 | 56 |
| AS54005 | ZPro Solutions | Unclassified | IPv4 | 56 |
| AS398824 | Orillia Pronet, Inc. | Unclassified | IPv4 | 56 |
| AS14116 | Internet Names For Business Inc. | Hosting | IPv4 | 40 |
| AS53334 | Total Uptime Technologies, LLC | Unclassified | IPv4 IPv6 | 21 |
| AS19678 | Intus Smart Network Solutions Inc. | Unclassified | IPv6 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS19122 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 397 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 202 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 135 |
| AS18588 | Postmedia Network Inc | Hosting | IPv4 | 112 |
| AS54572 | Nasdaq, Inc. | Unclassified | IPv4 | 57 |
| AS27549 | Cloud at Work | Unclassified | IPv4 | 56 |
| AS54005 | ZPro Solutions | Unclassified | IPv4 | 56 |
| AS398824 | Orillia Pronet, Inc. | Unclassified | IPv4 | 56 |
| AS14116 | Internet Names For Business Inc. | Hosting | IPv4 | 40 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 30 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.