asn.dev

Observed topology

AS9516 SAKURALINK-AS-AP SAKURA LINK LIMITED

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS9516: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv699
AS4229Zenlayer IncHostingIPv64
AS21859Zenlayer IncHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49304SAKURA LINK LIMITEDUnclassifiedIPv4 IPv62,770
AS55999Shanghai Sakura Communications Co., Ltd.,UnclassifiedIPv4728
AS63150BAGE CLOUD LLCHostingIPv4 IPv6427
AS202069Sakura Communications LimitedUnclassifiedIPv4250
AS32135SAKURA LTD.UnclassifiedIPv485
AS151662SangforUnclassifiedIPv481

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS49304SAKURA LINK LIMITEDUnclassifiedIPv4 IPv69,768
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv67,224
AS4229Zenlayer IncHostingIPv4 IPv63,859
AS55999Shanghai Sakura Communications Co., Ltd.,UnclassifiedIPv4728
AS63150BAGE CLOUD LLCHostingIPv4 IPv6461
AS21859Zenlayer IncHostingIPv4 IPv6446
AS202069Sakura Communications LimitedUnclassifiedIPv4250
AS32135SAKURA LTD.UnclassifiedIPv485
AS151662SangforUnclassifiedIPv481
AS4743ISIF LIMITEDUnclassifiedIPv452

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.