Observed topology
AS60771 C-CORP-AS Comiten Corp LLC
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS60771: 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 |
|---|---|---|---|---|
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 522 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 119 |
| AS47656 | Ast-Systems Ltd. | Unclassified | IPv4 | 52 |
| AS8595 | OOO WestCall Ltd. | Unclassified | IPv4 | 41 |
| AS31200 | Novotelecom Ltd | Unclassified | IPv4 | 39 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 28 |
| AS60840 | OJSC Telecom-Service | Unclassified | IPv4 | 20 |
| AS24482 | SG.GS | Hosting | IPv4 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 9 |
| AS50509 | Transroute Telecom LTD | Unclassified | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS60771 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211616 | JSC RZD-Zdorovie | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS60771 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29076 | Citytelecom LLC | Hosting | IPv4 | 616 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 119 |
| AS211616 | JSC RZD-Zdorovie | Unclassified | IPv4 | 61 |
| AS47656 | Ast-Systems Ltd. | Unclassified | IPv4 | 52 |
| AS8595 | OOO WestCall Ltd. | Unclassified | IPv4 | 41 |
| AS31200 | Novotelecom Ltd | Unclassified | IPv4 | 39 |
| AS39153 | JOINT-STOCK COMPANY "TELEPORT TELECOM" | Unclassified | IPv4 | 36 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 28 |
| AS60840 | OJSC Telecom-Service | Unclassified | IPv4 | 20 |
| AS24482 | SG.GS | Hosting | IPv4 | 10 |
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.