asn.dev

Observed topology

AS204921 YunZheng-Network zhenyun sun

Unclassified RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS204921: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6183
AS11967Hop179 OUUnclassifiedIPv4 IPv6163
AS18423RAID Networks Co., Ltd.HostingIPv4 IPv6143
AS44324MoeDove LLCResidentialIPv4 IPv6112
AS199310XIN BING XIANHostingIPv675
AS20473The Constant Company, LLCHostingIPv4 IPv665
AS36530IDC CubeUnclassifiedIPv4 IPv655
AS204539Axivora Connect LtdResidentialIPv4 IPv637
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv635
AS216211CYBERVERSE LLCHostingIPv632

All 20 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208223SHU-HAO TUNGUnclassifiedIPv632

Adjacency

Adjacent networks

All 21

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6183
AS11967Hop179 OUUnclassifiedIPv4 IPv6163
AS18423RAID Networks Co., Ltd.HostingIPv4 IPv6149
AS44324MoeDove LLCResidentialIPv4 IPv6112
AS199310XIN BING XIANHostingIPv675
AS20473The Constant Company, LLCHostingIPv4 IPv665
AS36530IDC CubeUnclassifiedIPv4 IPv655
AS140096JINX CO., LIMITEDUnclassifiedIPv647
AS204539Axivora Connect LtdResidentialIPv4 IPv637
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv635

All 21 adjacent →

Provenance

Where this comes from

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