asn.dev

Observed topology

AS9198 KAZTELECOM-AS JSC Kazakhtelecom

Unclassified RIPE NSP

Upstreams 25 carry this network
Downstreams 81 this network carries
Adjacent (IPv4) 108
Adjacent (IPv6) 35
Upstream graph Who carries AS9198, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS9198 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 25

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.

ASNetworkTypeFamiliesPaths seen
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv618,604
AS23764CTGNetUnclassifiedIPv412,375
AS209141China Mobile International (Russia), LLCMobileIPv45,650
AS3356Level 3 Parent, LLCTransitIPv4 IPv65,013
AS1299Arelion Sweden ABTransitIPv4 IPv63,165
AS3491PCCW Global (HK) Ltd.TransitIPv43,077
AS174Cogent Communications, LLCTransitIPv4 IPv62,702
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv62,452
AS31133PJSC MegaFonMobileIPv41,853
AS9002RETN LimitedUnclassifiedIPv4 IPv61,323

Transit

Downstream networks

All 81

Networks for which AS9198 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS29355Kcell JSCUnclassifiedIPv4 IPv6143,277
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv617,727
AS39824JSC Alma TelecommunicationsUnclassifiedIPv4 IPv64,716
AS50482JSC KazakhtelecomUnclassifiedIPv42,500
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv62,060
AS43994SMARTNET TOOUnclassifiedIPv4 IPv61,593
AS41124BTcom Infocommunications Ltd.UnclassifiedIPv41,577
AS8393"ASTEL" JSCUnclassifiedIPv41,504
AS49791Newserverlife LLCHostingIPv4 IPv61,031
AS203087Fedinyak Sergey VyacheslavovichUnclassifiedIPv4 IPv6964

Adjacency

Adjacent networks

All 108

Every AS seen directly next to AS9198 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS29355Kcell JSCUnclassifiedIPv4 IPv6143,277
AS12389PJSC RostelecomResidentialIPv4 IPv680,186
AS3216PJSC "Vimpelcom"MobileIPv4 IPv658,299
AS31133PJSC MegaFonMobileIPv444,384
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv629,082
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv622,454
AS23764CTGNetUnclassifiedIPv412,438
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv69,951
AS209141China Mobile International (Russia), LLCMobileIPv4 IPv68,206
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv65,450

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.