asn.dev

Observed topology

AS17534 NSK - NSK Co.,Ltd.

Unclassified ARIN

Upstreams 8 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 9
Adjacent (IPv6) 5
Upstream graph Who carries AS17534, and who carries them, drawn as a map up to the transit-free core. 7 exchanges Where AS17534 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS17534: 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
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6525
AS2914NTT America, Inc.TransitIPv4 IPv6442
AS6939Hurricane Electric LLCTransitIPv4223
AS17676SoftBank Corp.MobileIPv4 IPv6135
AS24482SG.GSHostingIPv4 IPv625
AS9304HGC Global Communications LimitedHostingIPv4 IPv624
AS132132MyRepublic Ltd.ResidentialIPv422
AS9824JCOM Co., Ltd.ResidentialIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS7668Hokuriku Telecommunication Network Co.UnclassifiedIPv410

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2519ARTERIA Networks CorporationUnclassifiedIPv4 IPv6532
AS2914NTT America, Inc.TransitIPv4 IPv6442
AS6939Hurricane Electric LLCTransitIPv4223
AS17676SoftBank Corp.MobileIPv4 IPv6135
AS132132MyRepublic Ltd.ResidentialIPv439
AS24482SG.GSHostingIPv4 IPv625
AS7668Hokuriku Telecommunication Network Co.UnclassifiedIPv424
AS9304HGC Global Communications LimitedHostingIPv4 IPv624
AS9824JCOM Co., Ltd.ResidentialIPv410

Provenance

Where this comes from

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