Observed topology
AS43197 TT-Mobile-AS Closed Joint Stock Company TT mobile
Mobile RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS43197: 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.
Transit
Downstream networks
Networks for which AS43197 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43030 | Tajik Academician Research and Educational Network Association | Unclassified | IPv4 IPv6 | 521 |
| AS199303 | CJSC Spitamen Bank | Unclassified | IPv4 | 98 |
| AS54994 | Meteverse Limited. | Unclassified | IPv4 | 61 |
| AS211203 | State unitary enterprise "Savings bank of the Republic of Tajikistan "Amonatbonk"" | Unclassified | IPv4 | 56 |
| AS43077 | CJSC International Bank of Tajikistan | Unclassified | IPv4 | 21 |
| AS199793 | Bank Eskhata OJSC | Unclassified | IPv4 | 4 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43197 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS51346 | Opened Joint Stock Company "Tojiktelecom" | Unclassified | IPv4 IPv6 | 1,275 |
| AS43030 | Tajik Academician Research and Educational Network Association | Unclassified | IPv4 IPv6 | 521 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 388 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 342 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 170 |
| AS199303 | CJSC Spitamen Bank | Unclassified | IPv4 | 98 |
| AS54994 | Meteverse Limited. | Unclassified | IPv4 | 61 |
| AS211203 | State unitary enterprise "Savings bank of the Republic of Tajikistan "Amonatbonk"" | Unclassified | IPv4 | 56 |
| AS43077 | CJSC International Bank of Tajikistan | Unclassified | IPv4 | 21 |
| AS199793 | Bank Eskhata OJSC | Unclassified | IPv4 | 4 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-01 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.48M 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.