Observed topology
AS20764 RASCOM-AS CJSC RASCOM
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS20764: 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 |
|---|---|---|---|---|
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 59 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 54 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 44 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 38 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 29 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 20 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 14 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 12 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 9 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 7 |
Transit
Downstream networks
Networks for which AS20764 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29182 | JSC IOT | Hosting | IPv4 IPv6 | 4,950 |
| AS49505 | JSC Selectel | Hosting | IPv4 IPv6 | 3,839 |
| AS50340 | JSC Selectel | Hosting | IPv4 IPv6 | 3,654 |
| AS9123 | JSC "TIMEWEB" | Hosting | IPv4 IPv6 | 2,266 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 IPv6 | 1,887 |
| AS29124 | Iskratelecom JSC | Residential | IPv4 | 1,682 |
| AS56534 | Comfortel Ltd. | Unclassified | IPv4 IPv6 | 1,418 |
| AS41560 | UGMK-Telecom LLC | Unclassified | IPv4 | 1,275 |
| AS64439 | IT Outsourcing LLC | Unclassified | IPv4 IPv6 | 989 |
| AS35807 | SkyNet Ltd. | Unclassified | IPv4 IPv6 | 958 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20764 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 32,254 |
| AS51659 | LLC Baxet | Unclassified | IPv4 IPv6 | 24,846 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 20,214 |
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 19,071 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 16,257 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 15,649 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 12,737 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 12,332 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 12,035 |
| AS29049 | Delta Telecom Ltd | Residential | IPv4 IPv6 | 10,643 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.