Observed topology
AS701 UUNET - Verizon Business
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,512 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 8,817 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 8,351 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 7,737 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 5,733 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 2,993 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 1,968 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 1,944 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 1,934 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 987 |
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 | Techtel LMDS Comunicaciones Interactivas S.A. | Residential | IPv4 IPv6 | 47,533 |
| AS14080 | Telmex Colombia S.A. | Residential | IPv4 IPv6 | 16,939 |
| AS5650 | Frontier Communications of America, Inc. | Residential | IPv4 | 16,746 |
| AS22394 | Verizon Business | Mobile | IPv4 IPv6 | 13,649 |
| AS8151 | UNINET | Mobile | IPv4 IPv6 | 12,835 |
| AS7046 | Verizon Business | Unclassified | IPv4 IPv6 | 12,510 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 | 8,688 |
| AS4837 | CHINA UNICOM China169 Backbone | Mobile | IPv4 IPv6 | 6,141 |
| AS17676 | SoftBank Corp. | Mobile | IPv4 | 5,590 |
| AS2828 | Verizon Business | Unclassified | IPv4 | 4,872 |
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,030 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 123,096 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 119,326 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 104,494 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 102,901 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 88,395 |
| AS14080 | Telmex Colombia S.A. | Residential | IPv4 IPv6 | 82,670 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 78,875 |
| AS11664 | Techtel LMDS Comunicaciones Interactivas S.A. | Residential | IPv4 IPv6 | 55,300 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 | 38,131 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.