asn.dev

Observed topology

AS211509 RUDAKI-AS Rudakov Ihor

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211509: 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
AS8772Netassist International EOODUnclassifiedIPv686
AS29632Netassist International EOODUnclassifiedIPv643
AS357084b42 UGUnclassifiedIPv64
AS37989DCS1 Pte. Ltd.HostingIPv64
AS58057Securebit AGUnclassifiedIPv64

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS207301Roman SartovHostingIPv656
AS215887Serhiy BobrovUnclassifiedIPv635
AS204508Gatterer Manuel trading as MLGTUnclassifiedIPv634
AS214763Akshay RevankarUnclassifiedIPv64
AS216386Aleksandr KuznetsovUnclassifiedIPv62
AS12687User Association of Ukrainian Research and Academic Network URANUnclassifiedIPv61
AS199183Arjen Olaf EssinkUnclassifiedIPv61

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS8772Netassist International EOODUnclassifiedIPv6161
AS29632Netassist International EOODUnclassifiedIPv6114
AS207301Roman SartovHostingIPv656
AS215887Serhiy BobrovUnclassifiedIPv635
AS204508Gatterer Manuel trading as MLGTUnclassifiedIPv634
AS44324MoeDove LLCResidentialIPv625
AS37989DCS1 Pte. Ltd.HostingIPv612
AS58057Securebit AGUnclassifiedIPv612
AS12687User Association of Ukrainian Research and Academic Network URANUnclassifiedIPv65
AS357084b42 UGUnclassifiedIPv64

Provenance

Where this comes from

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