Observed topology
AS34602 STARLINK-AS Moscow, Russia
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS34602: 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 |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 580 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 472 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 164 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 150 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 60 |
| AS43298 | Storm Networks LLC | Unclassified | IPv4 | 60 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 29 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 23 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 21 |
Transit
Downstream networks
Networks for which AS34602 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59679 | Agenstvo po rasprostraneniu zarubejnih izdaniy OJSC | Unclassified | IPv4 IPv6 | 110 |
| AS58020 | TERSYS COMPANY LLC | Unclassified | IPv4 | 64 |
| AS202832 | JSC "ProBank" | Unclassified | IPv4 | 64 |
| AS203117 | MTK LLC | Unclassified | IPv4 | 64 |
| AS39238 | OKB PROGRESS LLC | Hosting | IPv4 | 44 |
| AS58072 | Zenon-Region Ltd. | Unclassified | IPv4 | 32 |
| AS58319 | Kazakov Aleksey Dmitrievich | Unclassified | IPv4 IPv6 | 16 |
Adjacency
Adjacent networks
Every AS seen directly next to AS34602 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 IPv6 | 796 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 | 472 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 265 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 IPv6 | 184 |
| AS59679 | Agenstvo po rasprostraneniu zarubejnih izdaniy OJSC | Unclassified | IPv4 IPv6 | 110 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 69 |
| AS58020 | TERSYS COMPANY LLC | Unclassified | IPv4 | 64 |
| AS202832 | JSC "ProBank" | Unclassified | IPv4 | 64 |
| AS203117 | MTK LLC | Unclassified | IPv4 | 64 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.