asn.dev

Observed topology

AS41275 LEALTA-AS Moscow, Russia

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 30

Networks observed carrying traffic for AS41275: 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
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6632
AS3216PJSC "Vimpelcom"MobileIPv4390
AS201706SERVICEPIPE LLCUnclassifiedIPv4236
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6197
AS31500Global Network Management IncUnclassifiedIPv464
AS12389PJSC RostelecomResidentialIPv462
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv449
AS34549meerfarbig GmbH & Co. KGHostingIPv444
AS28917Fiord Networks, UABUnclassifiedIPv427
AS24482SG.GSHostingIPv423

All 30 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS202289Lovitel LLCUnclassifiedIPv465

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS35598INETCOM CARRIER LLCUnclassifiedIPv4 IPv6664
AS3216PJSC "Vimpelcom"MobileIPv4396
AS201706SERVICEPIPE LLCUnclassifiedIPv4236
AS20764CJSC RASCOMUnclassifiedIPv4 IPv6206
AS31500Global Network Management IncUnclassifiedIPv466
AS202289Lovitel LLCUnclassifiedIPv465
AS12389PJSC RostelecomResidentialIPv462
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv452
AS34549meerfarbig GmbH & Co. KGHostingIPv446
AS28917Fiord Networks, UABUnclassifiedIPv430

All 31 adjacent →

Provenance

Where this comes from

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