asn.dev

Observed topology

AS20661 TURKMENTELECOM-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS20661: 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
AS29049Delta Telecom LtdResidentialIPv4 IPv6569
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4339
AS12389PJSC RostelecomResidentialIPv4312

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS59974Altyn Asyr CJSCUnclassifiedIPv462
AS201558The State Bank for Foreign Affairs of TurkmenistanUnclassifiedIPv462
AS204579Turkmen hemrasi CJSCUnclassifiedIPv462
AS215487Tehno Merkez CJSCUnclassifiedIPv462
AS219194Turkmendomain Economic SocietyUnclassifiedIPv462

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS29049Delta Telecom LtdResidentialIPv4 IPv6718
AS12389PJSC RostelecomResidentialIPv4409
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4405
AS59974Altyn Asyr CJSCUnclassifiedIPv462
AS201558The State Bank for Foreign Affairs of TurkmenistanUnclassifiedIPv462
AS204579Turkmen hemrasi CJSCUnclassifiedIPv462
AS215487Tehno Merkez CJSCUnclassifiedIPv462
AS219194Turkmendomain Economic SocietyUnclassifiedIPv462
AS51495Telephone Network of Ashgabat CJSCUnclassifiedIPv42

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-25 12: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.