AS9198JSC Kazakhtelecom
As of 26th September 2026, AS9198 (JSC Kazakhtelecom), an access network registered in Kazakhstan with RIPE NCC, originates 1,097 IPv4 prefixes covering 3.5M addresses and 3 IPv6 prefixes. By IPv4 address space that makes it the 177th-largest of the 79,516 networks we see originating IPv4, and the largest of 212 in Kazakhstan. It is seen behind 20 upstream networks, most often AS12389 (Rostelecom PJSC) and AS3356 (Lumen (Level 3)), and in front of 81 downstream networks. Over 99% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. 93% of its routes reach at least 90% of full-feed peers, and 29 prefixes are also originated by another network.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS9198 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS9198 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.
Neighbouring networks
1,109
adjacent networks
- Upstreams
- 202%
- Peers
- 1,00891%
- Downstreams
- 817%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS12389Rostelecom PJSC | Peer | 89,677 | 142 | |
| AS3356Lumen (Level 3) | Peer | 62,797 | 82 | |
| AS31133MegaFon PJSC | Peer | 56,040 | 76 | |
| AS9002RETN Limited | Peer | 37,377 | 80 | |
| AS3216Vimpelcom PJSC | Peer | 36,475 | 77 | |
| AS174Cogent Communications, LLC | Peer | 22,052 | 40 | |
| AS43727JSC KVANT-TELEKOM | Peer | 20,291 | 85 | |
| AS23764China Telecom Global | Peer | 14,523 | 38 | |
| AS20485TransTeleCom JSC | Peer | 13,620 | 87 | |
| AS1299Arelion (fka. Telia Carrier) | Peer | 4,508 | 43 |
Prefixes
All 1,100The largest blocks AS9198 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 2.132.0.0/14 | 262k | 81/81 |
| 95.56.0.0/14 | 262k | 81/81 |
| 178.88.0.0/14 | 262k | 81/81 |
| 37.150.0.0/15 | 131k | 81/81 |
| 92.46.0.0/15 | 131k | 1/81 |
| 5.76.0.0/16 | 65.5k | 81/81 |
| 5.251.0.0/16 | 65.5k | 81/81 |
| 89.218.0.0/16 | 65.5k | 81/81 |
| 95.56.0.0/16 | 65.5k | 81/81 |
| 95.59.0.0/16 | 65.5k | 80/81 |
Routing health
How AS9198's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.
RPKI origin validation
- Valid99.7%1,097
- Invalid0.0%0
- No ROA0.3%3
Propagation
- Globally propagated90% of full-feed peers or more92.7%1,020
- Partially propagated40% to 90%<0.1%1
- Seen by few peersUnder 40%7.2%79
Prefix sizes
IPv4 — 1,097 prefixes
IPv6 — 3 prefixes
- /324.3B × /6433.3%1
- /4865.5k × /6466.7%2
Recent changes
Announcements that started or stopped since 28th Aug 2026.
- Announced212.154.128.0/1922nd Sept 2026
- Announced212.154.208.0/2122nd Sept 2026
- Announced212.154.209.0/2422nd Sept 2026
- Announced212.154.240.0/2322nd Sept 2026
- Announced212.154.243.0/2422nd Sept 2026
- Announced89.218.16.0/2422nd Sept 2026
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.