asn.dev

Observed topology

AS47139 INDIGO-TAJIKISTAN-AS CJSC INDIGO TAJIKISTAN

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS47139: 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 RostelecomResidentialIPv4 IPv6514
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4471
AS51346Opened Joint Stock Company "Tojiktelecom"UnclassifiedIPv4 IPv6131
AS48887CJSC INDIGO TAJIKISTANUnclassifiedIPv4124

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS48887CJSC INDIGO TAJIKISTANUnclassifiedIPv4 IPv6198
AS205507NURI KOINOT LLCUnclassifiedIPv449
AS57443Oshno group LLCUnclassifiedIPv435

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS28910"Uzbektelekom" Joint Stock CompanyUnclassifiedIPv4799
AS12389PJSC RostelecomResidentialIPv4 IPv6584
AS48887CJSC INDIGO TAJIKISTANUnclassifiedIPv4 IPv6322
AS57443Oshno group LLCUnclassifiedIPv4157
AS51346Opened Joint Stock Company "Tojiktelecom"UnclassifiedIPv4 IPv6137
AS205507NURI KOINOT LLCUnclassifiedIPv449

Provenance

Where this comes from

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