asn.dev

Observed topology

AS216299 LCNET Liuchang Network

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS216299: 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
AS44324MoeDove LLCResidentialIPv6126
AS52025ParadoxNetworks LimitedUnclassifiedIPv678
AS199310XIN BING XIANHostingIPv675
AS6939Hurricane Electric LLCTransitIPv673
AS53667FranTech SolutionsHostingIPv672
AS206069Cornseed LimitedResidentialIPv672
AS207529NYANLOLI LTDUnclassifiedIPv656
AS27523Kawaii Networks LLCUnclassifiedIPv637
AS216211CYBERVERSE LLCHostingIPv636
AS7720Skywolf Technology LLCUnclassifiedIPv632

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS201386MYRNA MISAKA NETWORK INCResidentialIPv633

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS44324MoeDove LLCResidentialIPv6127
AS52025ParadoxNetworks LimitedUnclassifiedIPv678
AS199310XIN BING XIANHostingIPv675
AS6939Hurricane Electric LLCTransitIPv673
AS53667FranTech SolutionsHostingIPv672
AS206069Cornseed LimitedResidentialIPv672
AS7720Skywolf Technology LLCUnclassifiedIPv664
AS207529NYANLOLI LTDUnclassifiedIPv656
AS27523Kawaii Networks LLCUnclassifiedIPv637
AS216211CYBERVERSE LLCHostingIPv636

All 23 adjacent →

Provenance

Where this comes from

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