asn.dev

Observed topology

AS21030 CDNNOW-AS Cluster LLC

Hosting RIPE

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

Transit

Upstream networks

All 18

Networks observed carrying traffic for AS21030: 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
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv4163
AS39572DataWeb Global Group B.V.HostingIPv4158
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv6146
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6112
AS3216PJSC "Vimpelcom"MobileIPv474
AS6939Hurricane Electric LLCTransitIPv447
AS20485Joint Stock Company TransTeleComUnclassifiedIPv445
AS20764CJSC RASCOMUnclassifiedIPv4 IPv614
AS59627Docker LTDUnclassifiedIPv413
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv49

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12567GAIJIN NETWORK LTDUnclassifiedIPv460
AS208981Data Center LLCUnclassifiedIPv411
AS48989Cluster LLCUnclassifiedIPv43

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS39572DataWeb Global Group B.V.HostingIPv4187
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv4163
AS62255BiMajLink d.o.o.UnclassifiedIPv4 IPv6146
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6112
AS3216PJSC "Vimpelcom"MobileIPv474
AS12567GAIJIN NETWORK LTDUnclassifiedIPv460
AS6939Hurricane Electric LLCTransitIPv447
AS20485Joint Stock Company TransTeleComUnclassifiedIPv445
AS206446CLOUD LEASE LtdHostingIPv438
AS48858JSC "ER-Telecom Holding"UnclassifiedIPv419

Provenance

Where this comes from

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