asn.dev

Observed topology

AS25159 SONICDUO-AS PJSC MegaFon

Unclassified ARIN

Upstreams 1 carry this network
Downstreams 53 this network carries
Adjacent (IPv4) 53
Adjacent (IPv6) 3
Upstream graph Who carries AS25159, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS25159 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

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.

ASNetworkTypeFamiliesPaths seen
AS31133PJSC MegaFonMobileIPv4 IPv64,764

Transit

Downstream networks

All 53

Networks for which AS25159 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS24866PJSC MegaFonUnclassifiedIPv4354
AS51288Web3tel msk OOOUnclassifiedIPv4196
AS8263PJSC MegaFonUnclassifiedIPv4177
AS30853Main Radio Meteorological Centre (MRMC)UnclassifiedIPv4174
AS207984Crazy Panda Rus Ltd.UnclassifiedIPv4166
AS210239The M.I. Krivosheev National Research Centre for TelecommunicationUnclassifiedIPv4116
AS39154Business-Finance LLCUnclassifiedIPv4112
AS211076PJSC NOVATEKUnclassifiedIPv494
AS51339'ARKTIKA GROUP' LtdUnclassifiedIPv475
AS212211CDEK-Global LLCUnclassifiedIPv464

Adjacency

Adjacent networks

All 54

Every AS seen directly next to AS25159 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS31133PJSC MegaFonMobileIPv4 IPv67,567
AS24866PJSC MegaFonUnclassifiedIPv4354
AS25189AO CountrycomUnclassifiedIPv4234
AS51288Web3tel msk OOOUnclassifiedIPv4196
AS8263PJSC MegaFonUnclassifiedIPv4177
AS30853Main Radio Meteorological Centre (MRMC)UnclassifiedIPv4174
AS207984Crazy Panda Rus Ltd.UnclassifiedIPv4166
AS210239The M.I. Krivosheev National Research Centre for TelecommunicationUnclassifiedIPv4116
AS39154Business-Finance LLCUnclassifiedIPv4112
AS211076PJSC NOVATEKUnclassifiedIPv494

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.