Observed topology
AS8641 NAUKANET-AS LLC "Nauka-Svyaz"
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS8641: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 999 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 518 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 428 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 338 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 208 |
| AS210756 | EdgeCenter LLC | Hosting | IPv4 | 197 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 157 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 154 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 153 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 55 |
Transit
Downstream networks
Networks for which AS8641 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS61121 | Gruppa Kompani GEOTEL AO | Residential | IPv4 IPv6 | 1,257 |
| AS42892 | PE Filimonov Boris Yurievich | Residential | IPv4 | 707 |
| AS28809 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 630 |
| AS197460 | Zencom LTD | Unclassified | IPv4 | 512 |
| AS34829 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 504 |
| AS44622 | Mifril+ LLC | Unclassified | IPv4 | 501 |
| AS49377 | ARCTIC TELECOM Limited Liability Company | Unclassified | IPv4 | 501 |
| AS42484 | LLC "Nauka-Svyaz" | Unclassified | IPv4 | 441 |
| AS50265 | Invest Mobile LLC | Unclassified | IPv4 IPv6 | 369 |
| AS199361 | LLC Mixplat Processing | Unclassified | IPv4 | 318 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8641 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 7,531 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 3,088 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,464 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 1,662 |
| AS61121 | Gruppa Kompani GEOTEL AO | Residential | IPv4 IPv6 | 1,309 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 1,301 |
| AS44020 | Modern Solutions LTD | Unclassified | IPv4 IPv6 | 1,210 |
| AS44622 | Mifril+ LLC | Unclassified | IPv4 | 1,165 |
| AS215601 | Innovative IT Solutions LLC | Unclassified | IPv4 IPv6 | 1,086 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,044 |
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.