asn.dev

Observed topology

AS44391 ESD-AS JSC Elektrosvyaz

Unclassified RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS44391: 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 IPv61,348
AS6939Hurricane Electric LLCTransitIPv4519
AS12389PJSC RostelecomResidentialIPv4 IPv6438
AS3216PJSC "Vimpelcom"MobileIPv4375
AS8359MTS PJSCMobileIPv4 IPv6252
AS43727JSC KVANT-TELEKOMResidentialIPv459
AS37721Virtual Technologies & SolutionsResidentialIPv455
AS24482SG.GSHostingIPv450
AS49673Truenetwork LLCUnclassifiedIPv450
AS8218Zayo Infrastructure France SAUnclassifiedIPv448

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS58134JSC ElektrosvyazUnclassifiedIPv459
AS207423STEIL-SOUTH LTDUnclassifiedIPv419
AS64492Partner-Service LLCUnclassifiedIPv4 IPv63

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS31133PJSC MegaFonMobileIPv4 IPv61,349
AS6939Hurricane Electric LLCTransitIPv4529
AS12389PJSC RostelecomResidentialIPv4 IPv6438
AS3216PJSC "Vimpelcom"MobileIPv4394
AS8359MTS PJSCMobileIPv4 IPv6295
AS43727JSC KVANT-TELEKOMResidentialIPv459
AS58134JSC ElektrosvyazUnclassifiedIPv459
AS37721Virtual Technologies & SolutionsResidentialIPv456
AS24482SG.GSHostingIPv451
AS49673Truenetwork LLCUnclassifiedIPv451

All 19 adjacent →

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.