asn.dev

Observed topology

AS44158 ALTURA-AS "Altura" ltd.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44158: 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
AS60299Mezhdugorodnyaya Mezhdunarodnaya Telefonnaya Stanciya Ltd.UnclassifiedIPv434
AS57304JSC "RetnNet"UnclassifiedIPv426
AS43727JSC KVANT-TELEKOMResidentialIPv42

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44552"Altura" ltd.UnclassifiedIPv4141
AS39256Dom-TV LLCUnclassifiedIPv497
AS34703LTD Pokrovsky radiotelefonUnclassifiedIPv490
AS61971SarLink LLCUnclassifiedIPv452

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS43727JSC KVANT-TELEKOMResidentialIPv4250
AS57304JSC "RetnNet"UnclassifiedIPv4152
AS44552"Altura" ltd.UnclassifiedIPv4141
AS39256Dom-TV LLCUnclassifiedIPv497
AS34703LTD Pokrovsky radiotelefonUnclassifiedIPv490
AS61971SarLink LLCUnclassifiedIPv452
AS60299Mezhdugorodnyaya Mezhdunarodnaya Telefonnaya Stanciya Ltd.UnclassifiedIPv440

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.