Observed topology
AS211509 RUDAKI-AS Rudakov Ihor
Unclassified RIPE NSP
Transit
Upstream networks
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.
Transit
Downstream networks
Networks for which AS211509 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS207301 | Roman Sartov | Hosting | IPv6 | 56 |
| AS204508 | Gatterer Manuel trading as MLGT | Unclassified | IPv6 | 33 |
| AS215887 | Serhiy Bobrov | Unclassified | IPv6 | 33 |
| AS197000 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv6 | 6 |
| AS214763 | Akshay Revankar | Unclassified | IPv6 | 3 |
| AS216386 | Aleksandr Kuznetsov | Unclassified | IPv6 | 2 |
| AS59449 | Mitja Herbaj | Unclassified | IPv6 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS211509 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8772 | Netassist International EOOD | Unclassified | IPv6 | 155 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 91 |
| AS207301 | Roman Sartov | Hosting | IPv6 | 56 |
| AS204508 | Gatterer Manuel trading as MLGT | Unclassified | IPv6 | 33 |
| AS215887 | Serhiy Bobrov | Unclassified | IPv6 | 33 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv6 | 14 |
| AS58057 | Securebit AG | Unclassified | IPv6 | 14 |
| AS44324 | MoeDove LLC | Residential | IPv6 | 8 |
| AS197000 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv6 | 6 |
| AS35708 | 4b42 UG | Unclassified | IPv6 | 4 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.