Observed topology
AS197068 CURATOR
Hosting RIPE Network Services
Transit
Upstream networks
Networks observed carrying traffic for AS197068: 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 |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 298 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 132 |
| AS8359 | MTS PJSC | Mobile | IPv4 IPv6 | 126 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 75 |
| AS49800 | GNC-Alfa CJSC | Residential | IPv6 | 38 |
| AS200590 | NLS Kazakhstan LLC | Unclassified | IPv6 | 35 |
| AS9049 | JSC "ER-Telecom Holding" | Unclassified | IPv4 | 23 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 22 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 8 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 6 |
Transit
Downstream networks
Networks for which AS197068 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43247 | "YooMoney" NBCO LLC | Unclassified | IPv4 | 1,140 |
| AS51115 | HLL LLC | Unclassified | IPv4 IPv6 | 1,051 |
| AS201012 | KEH eCommerce LLC | Unclassified | IPv4 | 657 |
| AS56528 | BIG MMO GAME NETWORK LIMITED | Unclassified | IPv4 | 480 |
| AS212264 | Closed joint stock company "ZOLOTAYA KORONA" | Unclassified | IPv4 | 300 |
| AS34545 | Webinar Tehnologii OOO | Unclassified | IPv4 | 240 |
| AS39684 | OOO Mango Telecom | Unclassified | IPv4 | 240 |
| AS57319 | JSC "Tander" | Unclassified | IPv4 | 240 |
| AS43399 | "TBANK" JSC | Unclassified | IPv4 | 202 |
| AS41706 | PJSC NK Rosneft | Unclassified | IPv4 | 180 |
Adjacency
Adjacent networks
Every AS seen directly next to AS197068 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200449 | Qrator Labs CZ s.r.o. | Unclassified | IPv4 IPv6 | 7,911 |
| AS43247 | "YooMoney" NBCO LLC | Unclassified | IPv4 | 1,140 |
| AS51115 | HLL LLC | Unclassified | IPv4 IPv6 | 1,051 |
| AS201012 | KEH eCommerce LLC | Unclassified | IPv4 | 657 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 532 |
| AS56528 | BIG MMO GAME NETWORK LIMITED | Unclassified | IPv4 | 480 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 448 |
| AS43973 | QIWI JSC | Unclassified | IPv4 | 420 |
| AS57319 | JSC "Tander" | Unclassified | IPv4 | 302 |
| AS212264 | Closed joint stock company "ZOLOTAYA KORONA" | Unclassified | IPv4 | 300 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 74.36M 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.