Observed topology
AS7342 VERISIGN-AS
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS7342: 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 | 3,416 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 3,266 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,131 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 872 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 517 |
| AS15830 | Equinix (EMEA) Acquisition Enterprises B.V. | Hosting | IPv4 IPv6 | 404 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 390 |
| AS26134 | VeriSign Infrastructure & Operations | Unclassified | IPv4 IPv6 | 153 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 59 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 42 |
Transit
Downstream networks
Networks for which AS7342 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS36625 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 461 |
| AS396549 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 351 |
| AS396566 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 319 |
| AS36631 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 285 |
| AS19836 | VeriSign Infrastructure & Operations | Unclassified | IPv4 IPv6 | 254 |
| AS36629 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 153 |
| AS396555 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 121 |
| AS20172 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 117 |
| AS397203 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 102 |
| AS36628 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 99 |
Adjacency
Adjacent networks
Every AS seen directly next to AS7342 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 3,906 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 3,524 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,540 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,107 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,056 |
| AS36625 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 461 |
| AS15830 | Equinix (EMEA) Acquisition Enterprises B.V. | Hosting | IPv4 IPv6 | 404 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 390 |
| AS396549 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 351 |
| AS396566 | VeriSign Global Registry Services | Unclassified | IPv4 IPv6 | 319 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.