Observed topology
AS15493 RUSCOMP-AS "Russian company" LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS15493: 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 |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 2,445 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 906 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 359 |
| AS50923 | Metroset Ltd. | Residential | IPv4 IPv6 | 58 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 9 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 9 |
Transit
Downstream networks
Networks for which AS15493 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41469 | ZSRCT TECOS Ltd. | Unclassified | IPv4 | 877 |
| AS8998 | "Russian company" LLC | Unclassified | IPv4 | 119 |
| AS5387 | consulting" LLC | Unclassified | IPv4 | 64 |
| AS56405 | Ilya Borisovich Rakcheev PE | Unclassified | IPv4 | 63 |
| AS61009 | Tyumbit-ASU OOO | Unclassified | IPv4 | 62 |
| AS208774 | Joint Stock Company "TTS" | Unclassified | IPv4 | 35 |
| AS44847 | "Russian company" LLC | Unclassified | IPv4 | 17 |
| AS209099 | Limited Liability Company "NonStop" | Unclassified | IPv4 | 15 |
| AS57120 | TMK Ltd | Unclassified | IPv4 | 9 |
| AS204298 | AO TODEP | Unclassified | IPv4 | 7 |
Adjacency
Adjacent networks
Every AS seen directly next to AS15493 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 2,886 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 963 |
| AS41469 | ZSRCT TECOS Ltd. | Unclassified | IPv4 | 939 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 914 |
| AS50923 | Metroset Ltd. | Residential | IPv4 IPv6 | 269 |
| AS8998 | "Russian company" LLC | Unclassified | IPv4 | 119 |
| AS5387 | consulting" LLC | Unclassified | IPv4 | 64 |
| AS56405 | Ilya Borisovich Rakcheev PE | Unclassified | IPv4 | 63 |
| AS61009 | Tyumbit-ASU OOO | Unclassified | IPv4 | 62 |
| AS208774 | Joint Stock Company "TTS" | Unclassified | IPv4 | 35 |
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.