Observed topology

AS20661 TurkmenTelecom-AS State Company of Electro Communications Turkmentelecom

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.

AS	Network	Type	Families	Paths seen
AS29049	Delta Telecom Ltd	Residential	IPv4 IPv6	551
AS12389	PJSC Rostelecom	Residential	IPv4	355
AS28910	"Uzbektelekom" Joint Stock Company	Unclassified	IPv4	326

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS59974	Altyn Asyr CJSC	Unclassified	IPv4	63
AS201558	The State Bank for Foreign Affairs of Turkmenistan	Unclassified	IPv4	63
AS204579	Turkmen hemrasi CJSC	Unclassified	IPv4	63
AS215487	Tehno Merkez CJSC	Unclassified	IPv4	63
AS219194	Turkmendomain Economic Society	Unclassified	IPv4	63

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS29049	Delta Telecom Ltd	Residential	IPv4 IPv6	692
AS12389	PJSC Rostelecom	Residential	IPv4	473
AS28910	"Uzbektelekom" Joint Stock Company	Unclassified	IPv4	410
AS59974	Altyn Asyr CJSC	Unclassified	IPv4	63
AS201558	The State Bank for Foreign Affairs of Turkmenistan	Unclassified	IPv4	63
AS204579	Turkmen hemrasi CJSC	Unclassified	IPv4	63
AS215487	Tehno Merkez CJSC	Unclassified	IPv4	63
AS219194	Turkmendomain Economic Society	Unclassified	IPv4	63
AS51495	Telephone Network of Ashgabat CJSC	Unclassified	IPv4	28

Provenance

Where this comes from

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