Observed topology
AS701 UUNET
Residential DROP-listed space ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS701: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 10,569 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 8,824 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 8,791 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 7,892 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 5,772 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 3,019 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 1,982 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 1,948 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 1,941 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 994 |
Transit
Downstream networks
Networks for which AS701 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11664 | LMDS Comunicaciones Interactivas S.A. | Residential | IPv4 IPv6 | 45,673 |
| AS14080 | Colombia S.A. | Residential | IPv4 IPv6 | 17,188 |
| AS5650 | Frontier Communications of America, Inc. | Residential | IPv4 | 16,845 |
| AS22394 | Verizon Business | Mobile | IPv4 IPv6 | 13,728 |
| AS7046 | Verizon Business | Unclassified | IPv4 IPv6 | 12,654 |
| AS8151 | UNINET | Mobile | IPv4 IPv6 | 12,002 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 | 8,766 |
| AS4837 | CHINA UNICOM China169 Backbone | Mobile | IPv4 IPv6 | 6,539 |
| AS17676 | SoftBank Corp. | Mobile | IPv4 | 5,602 |
| AS2828 | Verizon Business | Unclassified | IPv4 | 5,013 |
Adjacency
Adjacent networks
Every AS seen directly next to AS701 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS22394 | Verizon Business | Mobile | IPv4 IPv6 | 194,913 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 124,253 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 113,889 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 112,985 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 105,400 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 89,910 |
| AS14080 | Colombia S.A. | Residential | IPv4 IPv6 | 82,953 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 78,415 |
| AS11664 | LMDS Comunicaciones Interactivas S.A. | Residential | IPv4 IPv6 | 53,260 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 | 38,053 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-27 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.06M 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.