asn.dev

Observed topology

AS9198 KAZTELECOM-AS JSC Kazakhtelecom

Unclassified RIPE

Upstreams 21 carry this network
Downstreams 81 this network carries
Adjacent (IPv4) 104
Adjacent (IPv6) 36
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 21

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,251
AS23764CTGNetUnclassifiedIPv411,921
AS209141China Mobile International (Russia), LLCMobileIPv46,028
AS3356Level 3 Parent, LLCTransitIPv4 IPv64,737
AS1299Arelion Sweden ABTransitIPv4 IPv64,266
AS3491PCCW Global (HK) Ltd.TransitIPv43,863
AS31133PJSC MegaFonMobileIPv43,094
AS174Cogent Communications, LLCTransitIPv4 IPv62,428
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv61,737
AS9002RETN LimitedUnclassifiedIPv4 IPv6885

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 IPv6145,622
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv617,684
AS39824JSC Alma TelecommunicationsUnclassifiedIPv4 IPv64,746
AS50482JSC KazakhtelecomUnclassifiedIPv42,490
AS43994SMARTNET TOOUnclassifiedIPv4 IPv61,659
AS8393"ASTEL" JSCUnclassifiedIPv41,587
AS41124BTcom Infocommunications Ltd.UnclassifiedIPv41,561
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv61,530
AS49791Newserverlife LLCHostingIPv4 IPv61,031
AS203087Fedinyak Sergey VyacheslavovichUnclassifiedIPv4 IPv6920

Adjacency

Adjacent networks

All 104

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

ASNetworkTypeFamiliesPaths seen
AS29355Kcell JSCUnclassifiedIPv4 IPv6145,622
AS12389PJSC RostelecomResidentialIPv4 IPv6103,378
AS31133PJSC MegaFonMobileIPv4 IPv642,503
AS3216PJSC "Vimpelcom"MobileIPv4 IPv641,664
AS43727JSC KVANT-TELEKOMResidentialIPv4 IPv628,837
AS48503Mobile Telecom-Service LLPUnclassifiedIPv4 IPv622,445
AS23764CTGNetUnclassifiedIPv411,986
AS20485Joint Stock Company TransTeleComUnclassifiedIPv4 IPv69,012
AS209141China Mobile International (Russia), LLCMobileIPv4 IPv67,228
AS39824JSC Alma TelecommunicationsUnclassifiedIPv4 IPv65,126

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.