asn.dev

Observed topology

AS215502 XING_QINGYU

Unclassified RIPE Educational/Research

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS215502: 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
AS16509Amazon.com, Inc.HostingIPv6307
AS7720Skywolf Technology LLCUnclassifiedIPv4 IPv697
AS44324MoeDove LLCResidentialIPv4 IPv693
AS47272HYEHOST LLCHostingIPv677
AS53667FranTech SolutionsHostingIPv674
AS199310XIN BING XIANHostingIPv640
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv637
AS17433Hytron Network Services LimitedResidentialIPv635
AS31898Oracle CorporationHostingIPv634
AS63473HostHatch, LLCUnclassifiedIPv634

All 15 upstreams →

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS16509Amazon.com, Inc.HostingIPv6307
AS7720Skywolf Technology LLCUnclassifiedIPv4 IPv697
AS44324MoeDove LLCResidentialIPv4 IPv693
AS47272HYEHOST LLCHostingIPv677
AS53667FranTech SolutionsHostingIPv674
AS199310XIN BING XIANHostingIPv640
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv637
AS17433Hytron Network Services LimitedResidentialIPv635
AS31898Oracle CorporationHostingIPv634
AS63473HostHatch, LLCUnclassifiedIPv634

All 15 adjacent →

Provenance

Where this comes from

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