asn.dev

Observed topology

AS44265 SMOLTELECOM-NET

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44265: 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
AS12389PJSC RostelecomResidentialIPv4270
AS31133PJSC MegaFonMobileIPv4140
AS3216PJSC "Vimpelcom"MobileIPv456
AS20485Joint Stock Company TransTeleComUnclassifiedIPv430

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS49336Zlato Telecom-Smolensk LtdUnclassifiedIPv462
AS57212Mercury LLCUnclassifiedIPv432

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS12389PJSC RostelecomResidentialIPv4335
AS31133PJSC MegaFonMobileIPv4144
AS3216PJSC "Vimpelcom"MobileIPv466
AS49336Zlato Telecom-Smolensk LtdUnclassifiedIPv462
AS20485Joint Stock Company TransTeleComUnclassifiedIPv445
AS57212Mercury LLCUnclassifiedIPv432

Provenance

Where this comes from

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