Observed topology
AS12418 QUANTUM
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS12418: 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 | 3,467 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 2,500 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1,051 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 836 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 793 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 685 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 595 |
| AS28825 | CJSC Telekommunikacii 21 | Unclassified | IPv4 | 416 |
| AS8595 | OOO WestCall Ltd. | Unclassified | IPv4 | 320 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 264 |
Transit
Downstream networks
Networks for which AS12418 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31703 | Mobil-group ltd | Hosting | IPv4 | 171 |
| AS213457 | Femco-Management LTD | Unclassified | IPv4 | 60 |
| AS57573 | JSC "Greenatom" | Unclassified | IPv4 | 59 |
| AS200054 | Joint Stock Company Bank "United Capital" | Unclassified | IPv4 | 42 |
| AS210787 | CDEK-Global LLC | Unclassified | IPv4 | 21 |
| AS51977 | FGBU ROSGEOLFOND | Unclassified | IPv4 | 19 |
| AS206845 | "FSBI "SCCS of A. N. Bakulev" of the Ministry of Health of the Russian Federation" | Unclassified | IPv4 | 17 |
| AS58163 | JSC Eksar | Unclassified | IPv4 | 12 |
| AS212491 | Continent Express JSC | Unclassified | IPv4 | 11 |
| AS48890 | SOLVO ltd | Unclassified | IPv4 | 5 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12418 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 3,467 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 2,500 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 1,051 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 988 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 815 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 760 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 595 |
| AS28825 | CJSC Telekommunikacii 21 | Unclassified | IPv4 | 416 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 346 |
| AS8595 | OOO WestCall Ltd. | Unclassified | IPv4 | 320 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.