asn.dev

Observed topology

AS58172 FreedomTelecom-AS Freedom Telecom Operations LLP

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS58172: 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
AS39824JSC Alma TelecommunicationsUnclassifiedIPv4 IPv63,138
AS35168TNS-Plus LLPUnclassifiedIPv4 IPv61,539
AS41798JSC TranstelecomUnclassifiedIPv4 IPv6912
AS205516NLS ASTANA LLPUnclassifiedIPv458

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS213841Network Telecom Systems LLPUnclassifiedIPv4125
AS8393"ASTEL" JSCUnclassifiedIPv4106
AS2035307sat LLPUnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS39824JSC Alma TelecommunicationsUnclassifiedIPv4 IPv63,206
AS35168TNS-Plus LLPUnclassifiedIPv4 IPv61,663
AS41798JSC TranstelecomUnclassifiedIPv4 IPv61,017
AS213841Network Telecom Systems LLPUnclassifiedIPv4125
AS8393"ASTEL" JSCUnclassifiedIPv4106
AS2035307sat LLPUnclassifiedIPv462
AS205516NLS ASTANA LLPUnclassifiedIPv458

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.