Observed topology
AS703 UUNET - Verizon Business
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS703: 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 |
|---|---|---|---|---|
| AS701 | Verizon Business | Residential | IPv4 IPv6 | 853 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 684 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 460 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 174 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 137 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 82 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 74 |
| AS18041 | Taiwan Digital Streaming Co. | Hosting | IPv4 IPv6 | 49 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 47 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 45 |
Transit
Downstream networks
Networks for which AS703 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9555 | Verizon Australia PTY Limited | Unclassified | IPv4 IPv6 | 1,936 |
| AS9466 | UUNET Japan Limited | Unclassified | IPv4 IPv6 | 1,239 |
| AS7722 | TELPACIFIC P/L | Unclassified | IPv4 | 532 |
| AS36224 | HCL AMERICA INC | Unclassified | IPv4 | 531 |
| AS31872 | Vantive Health | Unclassified | IPv4 | 413 |
| AS6256 | Verizon Business | Unclassified | IPv4 | 358 |
| AS395753 | KKR | Unclassified | IPv4 | 348 |
| AS3738 | State Street Bank and Trust Company | Unclassified | IPv4 | 344 |
| AS397074 | Marshalls | Unclassified | IPv4 | 318 |
| AS45903 | CMC Telecom Infrastructure Company | Residential | IPv4 | 313 |
Adjacency
Adjacent networks
Every AS seen directly next to AS703 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS701 | Verizon Business | Residential | IPv4 IPv6 | 4,544 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 4,166 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,419 |
| AS9555 | Verizon Australia PTY Limited | Unclassified | IPv4 IPv6 | 1,936 |
| AS9466 | UUNET Japan Limited | Unclassified | IPv4 IPv6 | 1,239 |
| AS1321 | Verizon Business | Unclassified | IPv4 IPv6 | 991 |
| AS36224 | HCL AMERICA INC | Unclassified | IPv4 | 735 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 672 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 608 |
| AS7722 | TELPACIFIC P/L | Unclassified | IPv4 | 532 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-04 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.33M 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.