asn.dev

Observed topology

AS206069 CORNSEED

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS206069: 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
AS216211CYBERVERSE LLCHostingIPv4 IPv6304
AS40792CYBERVERSEUnclassifiedIPv4 IPv6120

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219332Xiang ZhouUnclassifiedIPv6181
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv4 IPv6143
AS202939Chimon Technology LtdResidentialIPv6106
AS216299Yang LiuchangUnclassifiedIPv672
AS202335Zhanrui TianUnclassifiedIPv670
AS197817Nyco Cloud Network LLCUnclassifiedIPv657
AS202396Zeng YukaiUnclassifiedIPv640
AS11421HYWUnclassifiedIPv4 IPv623
AS151245China Internet Network Information CenterUnclassifiedIPv417
AS210352Yijia XuResidentialIPv615

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS216211CYBERVERSE LLCHostingIPv4 IPv61,294
AS204211Shanghai Yingyun Network Technology Co., Ltd.UnclassifiedIPv4 IPv6573
AS40792CYBERVERSEUnclassifiedIPv4 IPv6281
AS219332Xiang ZhouUnclassifiedIPv6181
AS202939Chimon Technology LtdResidentialIPv6106
AS216299Yang LiuchangUnclassifiedIPv672
AS202335Zhanrui TianUnclassifiedIPv670
AS197817Nyco Cloud Network LLCUnclassifiedIPv658
AS202396Zeng YukaiUnclassifiedIPv640
AS11421HYWUnclassifiedIPv4 IPv623

All 15 adjacent →

Provenance

Where this comes from

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