asn.dev

Observed topology

AS7342 VERISIGN-AS

Unclassified ARIN

Upstreams 58 carry this network
Downstreams 42 this network carries
Adjacent (IPv4) 95
Adjacent (IPv6) 71
Upstream graph Who carries AS7342, and who carries them, drawn as a map up to the transit-free core. 17 exchanges Where AS7342 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 58

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.

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv63,189
AS1299Arelion Sweden ABTransitIPv4 IPv62,874
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,626
AS3257GTT Communications Inc.TransitIPv4 IPv6887
AS6939Hurricane Electric LLCTransitIPv4 IPv6503
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6409
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6397
AS26134VeriSign Infrastructure & OperationsUnclassifiedIPv4 IPv6155
AS9002RETN LimitedUnclassifiedIPv4 IPv659
AS24482SG.GSHostingIPv4 IPv642

Transit

Downstream networks

All 42

Networks for which AS7342 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS36625VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6478
AS396549VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6354
AS396566VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6321
AS36631VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6284
AS19836VeriSign Infrastructure & OperationsUnclassifiedIPv4 IPv6255
AS396555VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6149
AS36629VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6148
AS20172VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6111
AS397203VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6102
AS36628VeriSign Global Registry ServicesUnclassifiedIPv4 IPv699

Adjacency

Adjacent networks

All 100

Every AS seen directly next to AS7342 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv63,461
AS1299Arelion Sweden ABTransitIPv4 IPv63,370
AS3356Level 3 Parent, LLCTransitIPv4 IPv62,024
AS3257GTT Communications Inc.TransitIPv4 IPv61,122
AS6939Hurricane Electric LLCTransitIPv4 IPv61,053
AS36625VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6478
AS15830Equinix (EMEA) Acquisition Enterprises B.V.HostingIPv4 IPv6409
AS3491PCCW Global (HK) Ltd.TransitIPv4 IPv6397
AS396549VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6354
AS396566VeriSign Global Registry ServicesUnclassifiedIPv4 IPv6321

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-31 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.50M 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.