asn.dev

Observed topology

AS7516 TOHKNET TOHKnet Co.,Inc.

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS7516: 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
AS2516KDDI CORPORATIONMobileIPv4 IPv6234
AS2914NTT America, Inc.TransitIPv4 IPv6214
AS6939Hurricane Electric LLCTransitIPv480
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610
AS9002RETN LimitedUnclassifiedIPv49
AS20485Joint Stock Company TransTeleComUnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS131953NPO YutopianetUnclassifiedIPv425

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4 IPv6237
AS2516KDDI CORPORATIONMobileIPv4 IPv6236
AS6939Hurricane Electric LLCTransitIPv480
AS131953NPO YutopianetUnclassifiedIPv425
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610
AS9002RETN LimitedUnclassifiedIPv49
AS20485Joint Stock Company TransTeleComUnclassifiedIPv49

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-12 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.