Observed topology
AS25159 SONICDUO-AS PJSC MegaFon
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS25159: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 4,856 |
Transit
Downstream networks
Networks for which AS25159 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24866 | PJSC MegaFon | Unclassified | IPv4 | 366 |
| AS51288 | Web3tel msk OOO | Unclassified | IPv4 | 208 |
| AS8263 | PJSC MegaFon | Unclassified | IPv4 | 183 |
| AS30853 | Main Radio Meteorological Centre (MRMC) | Unclassified | IPv4 | 180 |
| AS207984 | Crazy Panda Rus Ltd. | Unclassified | IPv4 | 174 |
| AS210239 | The M.I. Krivosheev National Research Centre for Telecommunication | Unclassified | IPv4 | 118 |
| AS39154 | Business-Finance LLC | Unclassified | IPv4 | 96 |
| AS211076 | PJSC NOVATEK | Unclassified | IPv4 | 92 |
| AS51339 | 'ARKTIKA GROUP' Ltd | Unclassified | IPv4 | 77 |
| AS39678 | OOO ALL UP NET | Unclassified | IPv4 | 72 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25159 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 7,689 |
| AS24866 | PJSC MegaFon | Unclassified | IPv4 | 366 |
| AS25189 | AO Countrycom | Unclassified | IPv4 | 240 |
| AS51288 | Web3tel msk OOO | Unclassified | IPv4 | 208 |
| AS8263 | PJSC MegaFon | Unclassified | IPv4 | 183 |
| AS30853 | Main Radio Meteorological Centre (MRMC) | Unclassified | IPv4 | 180 |
| AS207984 | Crazy Panda Rus Ltd. | Unclassified | IPv4 | 174 |
| AS210239 | The M.I. Krivosheev National Research Centre for Telecommunication | Unclassified | IPv4 | 118 |
| AS39154 | Business-Finance LLC | Unclassified | IPv4 | 96 |
| AS211076 | PJSC NOVATEK | Unclassified | IPv4 | 92 |
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.