Adjacent networks
AS20919 DF Moscow
Unclassified RIPE
Adjacency
Adjacent networks
Every AS seen directly next to AS20919 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 409 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 181 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 147 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 | 85 |
| AS56982 | PJSC EL5-Energo | Unclassified | IPv4 | 59 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 27 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 14 |
| AS60177 | Limited Liability Company BUKMEKERSKAYA KONTORA PARI | Unclassified | IPv4 | 12 |
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.
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.