asn.dev

Observed topology

AS34352 MCN-AS MSN Telecom LLC

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS34352: 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
AS3216PJSC "Vimpelcom"MobileIPv4272
AS12389PJSC RostelecomResidentialIPv4207
AS31133PJSC MegaFonMobileIPv451
AS1299Arelion Sweden ABTransitIPv448
AS47569Erlang company Ltd.UnclassifiedIPv428
AS34470PortTelekom LLCUnclassifiedIPv424
AS8359MTS PJSCMobileIPv423
AS6939Hurricane Electric LLCTransitIPv619
AS24482SG.GSHostingIPv4 IPv64
AS49673Truenetwork LLCUnclassifiedIPv44

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS12790MSN Telecom LLCUnclassifiedIPv460

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS3216PJSC "Vimpelcom"MobileIPv4286
AS12389PJSC RostelecomResidentialIPv4235
AS1299Arelion Sweden ABTransitIPv464
AS12790MSN Telecom LLCUnclassifiedIPv460
AS31133PJSC MegaFonMobileIPv451
AS47569Erlang company Ltd.UnclassifiedIPv428
AS34470PortTelekom LLCUnclassifiedIPv424
AS8359MTS PJSCMobileIPv423
AS6939Hurricane Electric LLCTransitIPv619
AS24482SG.GSHostingIPv4 IPv65

All 12 adjacent →

Provenance

Where this comes from

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