asn.dev

Observed topology

AS210352 YIJIAXU

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210352: 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
AS7720Skywolf Technology LLCUnclassifiedIPv6114
AS216211CYBERVERSE LLCHostingIPv699
AS17433Hytron Network Services LimitedResidentialIPv676
AS44324MoeDove LLCResidentialIPv676
AS20473The Constant Company, LLCHostingIPv673
AS199310XIN BING XIANHostingIPv646
AS206069Cornseed LimitedResidentialIPv630
AS207529NYANLOLI LTDUnclassifiedIPv613
AS40792CYBERVERSEUnclassifiedIPv67
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214933Bingxin LiuUnclassifiedIPv6135
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv636

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS216211CYBERVERSE LLCHostingIPv6224
AS214933Bingxin LiuUnclassifiedIPv6135
AS7720Skywolf Technology LLCUnclassifiedIPv6115
AS44324MoeDove LLCResidentialIPv6100
AS17433Hytron Network Services LimitedResidentialIPv676
AS20473The Constant Company, LLCHostingIPv673
AS199310XIN BING XIANHostingIPv646
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv639
AS151673Chen XinyuUnclassifiedIPv633
AS205008Junqi HuangUnclassifiedIPv633

All 13 adjacent →

Provenance

Where this comes from

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