Observed topology
AS60764 TK-Telecom Telecom Samara LLC
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS60764: 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 |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 217 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 105 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 80 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 73 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 35 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 26 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 20 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 11 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 11 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS60764 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35032 | LLC SIP "NIS" | Residential | IPv4 IPv6 | 421 |
| AS56407 | Zhigulevsk Cable Network LLC | Unclassified | IPv4 | 248 |
| AS60072 | LLC EGS-Telecom | Unclassified | IPv4 | 180 |
| AS49136 | Telenet Ltd. | Unclassified | IPv4 | 146 |
| AS39042 | LLC Global Telecom Co | Unclassified | IPv4 | 141 |
| AS201211 | LLC "Drugoy Telecom" | Unclassified | IPv4 | 128 |
| AS212030 | SMARTS-CITIES LLC | Unclassified | IPv4 | 64 |
| AS215943 | FOTON LLC | Unclassified | IPv4 | 60 |
| AS203118 | Ezerdi LLC | Hosting | IPv4 IPv6 | 40 |
| AS44597 | Join-stock company "Internet Exchange"MSK-IX" | Unclassified | IPv4 | 23 |
Adjacency
Adjacent networks
Every AS seen directly next to AS60764 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 IPv6 | 700 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 569 |
| AS35032 | LLC SIP "NIS" | Residential | IPv4 IPv6 | 443 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 IPv6 | 282 |
| AS56407 | Zhigulevsk Cable Network LLC | Unclassified | IPv4 | 248 |
| AS201211 | LLC "Drugoy Telecom" | Unclassified | IPv4 | 189 |
| AS60072 | LLC EGS-Telecom | Unclassified | IPv4 | 180 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 179 |
| AS203118 | Ezerdi LLC | Hosting | IPv4 IPv6 | 177 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 165 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.