asn.dev

Observed topology

AS29648 COMLINE-AS PJSC MegaFon

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS29648: 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 IPv67,817

Transit

Downstream networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS44493Chelyabinsk-Signal LLCUnclassifiedIPv4216
AS34246PJSC Forward EnergyUnclassifiedIPv4190
AS12418Quantum CJSCUnclassifiedIPv4182
AS198303Limited liability company AbsolutUnclassifiedIPv4 IPv678
AS198350Siberian Internet Company LLCUnclassifiedIPv459
AS49966PJSC "T Plus"UnclassifiedIPv458
AS208945Ustek-Chelyabinsk JSCUnclassifiedIPv458
AS51633Novatek-Chelyabinsk LLCUnclassifiedIPv453
AS49845PJSC Forward EnergyUnclassifiedIPv438
AS202781IT Service LtdUnclassifiedIPv421

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS31133PJSC MegaFonMobileIPv4 IPv68,827
AS44493Chelyabinsk-Signal LLCUnclassifiedIPv4216
AS34246PJSC Forward EnergyUnclassifiedIPv4190
AS12418Quantum CJSCUnclassifiedIPv4182
AS198303Limited liability company AbsolutUnclassifiedIPv4 IPv678
AS198350Siberian Internet Company LLCUnclassifiedIPv459
AS49966PJSC "T Plus"UnclassifiedIPv458
AS208945Ustek-Chelyabinsk JSCUnclassifiedIPv458
AS51633Novatek-Chelyabinsk LLCUnclassifiedIPv453
AS49845PJSC Forward EnergyUnclassifiedIPv438

Provenance

Where this comes from

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