Observed topology
AS51346 TOJIKTELECOM-AS Opened Joint Stock Company "Tojiktelecom"
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS51346: 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 |
|---|---|---|---|---|
| AS205103 | Telegraph42 Management GmbH | Unclassified | IPv4 IPv6 | 365 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 240 |
| AS33962 | Citytelecom LLC | Hosting | IPv4 | 59 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 | 53 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 18 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 | 12 |
| AS24482 | SG.GS | Hosting | IPv4 | 10 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 8 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 6 |
| AS34019 | Hivane Association | Unclassified | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS51346 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8847 | CJSC "Telecomm Technology" | Unclassified | IPv4 | 1,127 |
| AS43197 | Closed Joint Stock Company TT mobile | Mobile | IPv4 IPv6 | 699 |
| AS49472 | Eastera LLC | Residential | IPv4 | 567 |
| AS44027 | Spitamen Alexander Internet LLC. | Unclassified | IPv4 | 453 |
| AS57443 | Oshno group LLC | Unclassified | IPv4 | 387 |
| AS204106 | CJSC Babilon-Mobile | Mobile | IPv4 IPv6 | 298 |
| AS47139 | CJSC INDIGO TAJIKISTAN | Unclassified | IPv4 IPv6 | 195 |
| AS42713 | INTERCOM LTD | Unclassified | IPv4 | 189 |
| AS196854 | LLC "Isatel" Tajikistan | Unclassified | IPv4 | 188 |
| AS215533 | LLC Zaitoon technology | Unclassified | IPv4 IPv6 | 166 |
Adjacency
Adjacent networks
Every AS seen directly next to AS51346 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 4,200 |
| AS204106 | CJSC Babilon-Mobile | Mobile | IPv4 IPv6 | 1,442 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 1,352 |
| AS205103 | Telegraph42 Management GmbH | Unclassified | IPv4 IPv6 | 1,237 |
| AS43197 | Closed Joint Stock Company TT mobile | Mobile | IPv4 IPv6 | 1,199 |
| AS8847 | CJSC "Telecomm Technology" | Unclassified | IPv4 | 1,127 |
| AS49472 | Eastera LLC | Residential | IPv4 | 567 |
| AS57443 | Oshno group LLC | Unclassified | IPv4 | 529 |
| AS44027 | Spitamen Alexander Internet LLC. | Unclassified | IPv4 | 518 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 320 |
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.