Observed topology
AS9198 KAZTELECOM-AS JSC Kazakhtelecom
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS9198: 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 |
|---|---|---|---|---|
| AS23764 | CTGNet | Unclassified | IPv4 | 12,338 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 IPv6 | 11,858 |
| AS209141 | China Mobile International (Russia), LLC | Mobile | IPv4 | 7,767 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 7,506 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,818 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 4,588 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,537 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 1,957 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,901 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,851 |
Transit
Downstream networks
Networks for which AS9198 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29355 | Kcell JSC | Unclassified | IPv4 IPv6 | 146,893 |
| AS48503 | Mobile Telecom-Service LLP | Unclassified | IPv4 IPv6 | 18,533 |
| AS39824 | JSC Alma Telecommunications | Unclassified | IPv4 IPv6 | 5,004 |
| AS200590 | NLS Kazakhstan LLC | Unclassified | IPv4 IPv6 | 3,831 |
| AS50482 | JSC Kazakhtelecom | Unclassified | IPv4 | 2,465 |
| AS8393 | "ASTEL" JSC | Unclassified | IPv4 | 2,258 |
| AS43994 | SMARTNET TOO | Unclassified | IPv4 IPv6 | 1,838 |
| AS41124 | BTcom Infocommunications Ltd. | Unclassified | IPv4 | 1,658 |
| AS49791 | Newserverlife LLC | Hosting | IPv4 IPv6 | 1,037 |
| AS203087 | Fedinyak Sergey Vyacheslavovich | Unclassified | IPv4 IPv6 | 904 |
Adjacency
Adjacent networks
Every AS seen directly next to AS9198 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS29355 | Kcell JSC | Unclassified | IPv4 IPv6 | 146,893 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 101,748 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 51,626 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 40,674 |
| AS43727 | JSC KVANT-TELEKOM | Residential | IPv4 IPv6 | 27,617 |
| AS48503 | Mobile Telecom-Service LLP | Unclassified | IPv4 IPv6 | 23,398 |
| AS23764 | CTGNet | Unclassified | IPv4 | 12,401 |
| AS209141 | China Mobile International (Russia), LLC | Mobile | IPv4 | 9,010 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 8,522 |
| AS200590 | NLS Kazakhstan LLC | Unclassified | IPv4 IPv6 | 7,341 |
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.