asn.dev

Observed topology

AS210352 YijiaXu Yijia Xu

Residential RIPE Cable/DSL/ISP

Upstreams 8 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 5
Adjacent (IPv6) 11
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 LLCUnclassifiedIPv4 IPv6143
AS216211CYBERVERSE LLCHostingIPv4 IPv6113
AS44324MoeDove LLCResidentialIPv4 IPv698
AS17433Hytron Network Services LimitedResidentialIPv4 IPv678
AS20473The Constant Company, LLCHostingIPv670
AS199310XIN BING XIANHostingIPv642
AS206069Cornseed LimitedResidentialIPv635
AS40792CYBERVERSEUnclassifiedIPv4 IPv69

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
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv636

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS7720Skywolf Technology LLCUnclassifiedIPv4 IPv6148
AS216211CYBERVERSE LLCHostingIPv4 IPv6141
AS44324MoeDove LLCResidentialIPv4 IPv6100
AS17433Hytron Network Services LimitedResidentialIPv4 IPv678
AS20473The Constant Company, LLCHostingIPv670
AS199310XIN BING XIANHostingIPv642
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv636
AS206069Cornseed LimitedResidentialIPv635
AS151673Chen XinyuUnclassifiedIPv632
AS205008Junqi HuangUnclassifiedIPv632

All 11 adjacent →

Provenance

Where this comes from

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