Observed topology
AS209030 KL-KDP AO Kaspersky Lab
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS209030: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 131 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 129 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 43 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 34 |
| AS3327 | CITIC Telecom CPC Netherlands B.V. | Unclassified | IPv4 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 | 1 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS209030 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34887 | Information Technology Center of the Republic of Tatarstan GUP | Unclassified | IPv4 | 236 |
| AS60388 | JSC "Oil Transportation and Production Telecommunications" | Residential | IPv4 | 177 |
| AS200107 | Kaspersky Lab Switzerland GmbH | Unclassified | IPv4 | 177 |
| AS203972 | LLC TatAISneft | Unclassified | IPv4 | 177 |
| AS44915 | All-Russian Regional Development Bank JSC | Unclassified | IPv4 | 118 |
| AS8484 | Novye oblachnye technologii LLC | Unclassified | IPv4 | 59 |
| AS15632 | JSC "Alfa-Bank" | Unclassified | IPv4 | 59 |
| AS50586 | CMRBank (LLC) | Unclassified | IPv4 | 59 |
| AS59434 | JSC "The Auction house of the Russian Federation" | Unclassified | IPv4 | 59 |
| AS196699 | Russ Outdoor LLC | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS209030 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 747 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 507 |
| AS34887 | Information Technology Center of the Republic of Tatarstan GUP | Unclassified | IPv4 | 236 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 191 |
| AS60388 | JSC "Oil Transportation and Production Telecommunications" | Residential | IPv4 | 177 |
| AS200107 | Kaspersky Lab Switzerland GmbH | Unclassified | IPv4 | 177 |
| AS203972 | LLC TatAISneft | Unclassified | IPv4 | 177 |
| AS44915 | All-Russian Regional Development Bank JSC | Unclassified | IPv4 | 118 |
| AS8484 | Novye oblachnye technologii LLC | Unclassified | IPv4 | 59 |
| AS15632 | JSC "Alfa-Bank" | Unclassified | IPv4 | 59 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.