Observed topology
AS51346 TOJIKTELECOM-AS
Unclassified RIPE NSP
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 | 500 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 89 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 | 65 |
| AS33962 | Citytelecom LLC | Hosting | IPv4 | 57 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 19 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 18 |
| AS29049 | Delta Telecom Ltd | Residential | IPv4 | 9 |
| AS17557 | Pakistan Telecommunication Company Limited | Unclassified | IPv4 | 6 |
| AS24482 | SG.GS | Hosting | 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,080 |
| AS43197 | Closed Joint Stock Company TT mobile | Mobile | IPv4 IPv6 | 768 |
| AS49472 | Eastera LLC | Residential | IPv4 | 558 |
| AS44027 | Spitamen Alexander Internet LLC. | Unclassified | IPv4 | 448 |
| AS57443 | Oshno group LLC | Unclassified | IPv4 | 399 |
| AS204106 | CJSC Babilon-Mobile | Mobile | IPv4 IPv6 | 254 |
| AS42713 | INTERCOM LTD | Unclassified | IPv4 | 186 |
| AS196854 | LLC "Isatel" Tajikistan | Unclassified | IPv4 | 185 |
| AS215533 | LLC Zaitoon technology | Unclassified | IPv4 IPv6 | 103 |
| AS63293 | Facebook, Inc. | Hosting | IPv4 IPv6 | 102 |
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 | 2,883 |
| AS205103 | Telegraph42 Management GmbH | Unclassified | IPv4 IPv6 | 1,770 |
| AS28910 | "Uzbektelekom" Joint Stock Company | Unclassified | IPv4 IPv6 | 1,584 |
| AS204106 | CJSC Babilon-Mobile | Mobile | IPv4 IPv6 | 1,427 |
| AS43197 | Closed Joint Stock Company TT mobile | Mobile | IPv4 IPv6 | 1,284 |
| AS8847 | CJSC "Telecomm Technology" | Unclassified | IPv4 | 1,080 |
| AS49472 | Eastera LLC | Residential | IPv4 | 558 |
| AS44027 | Spitamen Alexander Internet LLC. | Unclassified | IPv4 | 512 |
| AS57443 | Oshno group LLC | Unclassified | IPv4 | 489 |
| AS208592 | LLC "NET SOLUTIONS" | Unclassified | IPv4 | 361 |
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.