Observed topology
AS11071 IW-ASN-11071 - InfoWest
Residential ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS11071: 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 | 422 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 419 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 297 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 260 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 211 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 149 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 34 |
| AS7575 | Australian Academic and Research Network (AARNet) | Education | IPv4 | 26 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 26 |
Transit
Downstream networks
Networks for which AS11071 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS36815 | Internet FX | Hosting | IPv4 IPv6 | 385 |
| AS13824 | AireBeam | Unclassified | IPv4 | 185 |
| AS25840 | Cascade Access, LLC | Unclassified | IPv4 | 139 |
| AS20018 | Moapa Valley Telephone Company | Residential | IPv4 IPv6 | 126 |
| AS32808 | Utah Broadband LLC | Unclassified | IPv4 IPv6 | 95 |
| AS400134 | Balance of Nature | Unclassified | IPv4 | 55 |
| AS27448 | Kayenta Technologies | Unclassified | IPv4 | 26 |
Adjacency
Adjacent networks
Every AS seen directly next to AS11071 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 709 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 689 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 475 |
| AS36815 | Internet FX | Hosting | IPv4 IPv6 | 385 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 346 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 279 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 199 |
| AS13824 | AireBeam | Unclassified | IPv4 | 185 |
| AS25840 | Cascade Access, LLC | Unclassified | IPv4 | 139 |
| AS20018 | Moapa Valley Telephone Company | Residential | IPv4 IPv6 | 126 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.