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) 34
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
AS23764CTGNetUnclassifiedIPv412,338
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv611,858
AS209141China Mobile International (Russia), LLCMobileIPv47,767
AS31133PJSC MegaFonMobileIPv4 IPv67,506
AS3356Level 3 Parent, LLCTransitIPv4 IPv66,818
AS3491PCCW Global (HK) Ltd.TransitIPv44,588
AS174Cogent Communications, LLCTransitIPv4 IPv63,537
AS6939Hurricane Electric LLCTransitIPv41,957
AS1299Arelion Sweden ABTransitIPv4 IPv61,901
AS12389PJSC RostelecomResidentialIPv4 IPv61,851

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 IPv6146,893
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv618,533
AS39824JSC Alma TelecommunicationsUnclassifiedIPv4 IPv65,004
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv63,831
AS50482JSC KazakhtelecomUnclassifiedIPv42,465
AS8393"ASTEL" JSCUnclassifiedIPv42,258
AS43994SMARTNET TOOUnclassifiedIPv4 IPv61,838
AS41124BTcom Infocommunications Ltd.UnclassifiedIPv41,658
AS49791Newserverlife LLCHostingIPv4 IPv61,037
AS203087Fedinyak Sergey VyacheslavovichUnclassifiedIPv4 IPv6904

Adjacency

Adjacent networks

All 108

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

ASNetworkTypeFamiliesPaths seen
AS29355Kcell JSCUnclassifiedIPv4 IPv6146,893
AS12389PJSC RostelecomResidentialIPv4 IPv6101,748
AS31133PJSC MegaFonMobileIPv4 IPv651,626
AS3216PJSC "Vimpelcom"MobileIPv4 IPv640,674
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv627,617
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv623,398
AS23764CTGNetUnclassifiedIPv412,401
AS209141China Mobile International (Russia), LLCMobileIPv49,010
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv68,522
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv67,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.