asn.dev

Observed topology

AS23816 YAHOO LY Corporation

Hosting APNIC Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS23816: 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
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6231
AS2516KDDI CORPORATIONMobileIPv4 IPv6111
AS6939Hurricane Electric LLCTransitIPv462
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv421
AS17676SoftBank Corp.MobileIPv4 IPv615
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv68
AS24482SG.GSHostingIPv4 IPv68

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55898LY CorporationUnclassifiedIPv4 IPv6285
AS24296LY CorporationUnclassifiedIPv462
AS18140LY CorporationUnclassifiedIPv460

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4 IPv6441
AS55898LY CorporationUnclassifiedIPv4 IPv6285
AS2516KDDI CORPORATIONMobileIPv4 IPv6203
AS6939Hurricane Electric LLCTransitIPv4120
AS24296LY CorporationUnclassifiedIPv462
AS18140LY CorporationUnclassifiedIPv460
AS4713NTT DOCOMO BUSINESS,Inc.ResidentialIPv437
AS17676SoftBank Corp.MobileIPv4 IPv630
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv616
AS24482SG.GSHostingIPv4 IPv616

Provenance

Where this comes from

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