Network · data from 2026-11-12
AS50482 KAZAKHTELECOM-AS JSC Kazakhtelecom
Registry name: KAZAKHTELECOM-AS JSC Kazakhtelecom, KZ · not in PeeringDB
47IPv4 routes
100.0% RPKI valid · 27.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
34 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS50482, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS50482, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 212.154.164.0/24 | Valid | Nonecovered by 212.154.160.0/20 | 673 100% |
| 212.154.178.0/24 | Valid | None | 673 100% |
| 212.154.192.0/24 | Valid | None | 673 100% |
| 212.154.196.0/22 | Valid | None | 673 100% |
| 212.154.200.0/22 | Valid | None | 673 100% |
| 212.154.203.0/24 | Valid | None | 673 100% |
| 212.154.204.0/23 | Valid | None | 673 100% |
| 212.154.232.0/24 | Valid | None | 673 100% |
| 212.154.233.0/24 | Valid | None | 673 100% |
| 212.154.234.0/23 | Valid | None | 673 100% |
| 212.154.128.0/17 | Valid | None | 669 99% |
| 212.154.148.0/24 | Valid | Nonecovered by 212.154.128.0/19 | 669 99% |
| 212.154.166.0/24 | Valid | Nonecovered by 212.154.160.0/20 | 669 99% |
| 212.154.206.0/23 | Valid | None | 669 99% |
| 212.154.216.0/24 | Valid | None | 669 99% |
| 212.154.218.0/23 | Valid | None | 669 99% |
| 212.154.225.0/24 | Valid | None | 669 99% |
| 212.154.236.0/22 | Valid | None | 669 99% |
| 212.154.240.0/23 | Valid | None | 669 99% |
| 212.154.243.0/24 | Valid | None | 669 99% |
| 212.154.247.0/24 | Valid | None | 669 99% |
| 92.46.0.0/15 | Valid | Other origin only | 667 99% |
| 212.154.167.0/24 | Valid | Nonecovered by 212.154.160.0/20 | 642 95% |
| 212.154.174.0/24 | Valid | Nonecovered by 212.154.160.0/20 | 641 95% |
| 212.154.188.0/22 | Valid | None | 626 93% |
| 212.154.193.0/24 | Valid | None | 626 93% |
| 212.154.228.0/23 | Valid | None | 626 93% |
| 212.154.248.0/22 | Valid | None | 626 93% |
| 212.19.134.0/24 | Valid | Nonecovered by 212.19.128.0/20 | 546 81% |
| 212.154.211.0/24 | Valid | Nonecovered by 212.154.208.0/21 | 546 81% |
| 212.154.212.0/24 | Valid | Nonecovered by 212.154.208.0/21 | 545 81% |
| 212.154.137.0/24 | Valid | Nonecovered by 212.154.128.0/19 | 2 0%low visibility |
| 212.154.252.0/23 | Valid | None | 1 0%low visibility |
| 212.154.255.0/24 | Valid | None | 1 0%low visibility |
| 212.19.128.0/19 | Valid | RIR databaseRIPE | 667 99% |
| 212.154.160.0/20 | Valid | RIR databaseRIPE | 644 96% |
| 212.154.161.0/24 | Valid | RIR databaseRIPE | 644 96% |
| 212.154.176.0/23 | Valid | RIR databaseRIPE | 644 96% |
| 212.19.150.0/24 | Valid | RIR databaseRIPE | 642 95% |
| 212.154.209.0/24 | Valid | RIR databaseRIPE | 604 90% |
| 212.154.128.0/19 | Valid | RIR databaseRIPE | 603 90% |
| 212.154.208.0/21 | Valid | RIR databaseRIPE | 603 90% |
| 212.154.254.0/24 | Valid | RIR databaseRIPE | 603 90% |
| 212.19.128.0/20 | Valid | RIR databaseRIPE | 602 89% |
| 212.19.144.0/22 | Valid | RIR databaseRIPE | 602 89% |
| 212.19.149.0/24 | Valid | RIR databaseRIPE | 601 89% |
| 212.19.159.0/24 | Valid | RIR databaseRIPE | 601 89% |
AS-SET
AS50482 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 36 are in fix.csv.
- Route object: none34
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 212.154.164.0/24 | No route object for it. A route object for 212.154.160.0/20 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.178.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.192.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.196.0/22 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.200.0/22 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.203.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.204.0/23 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.232.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.233.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.234.0/23 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.128.0/17 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.148.0/24 | No route object for it. A route object for 212.154.128.0/19 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.166.0/24 | No route object for it. A route object for 212.154.160.0/20 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.206.0/23 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.216.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.218.0/23 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.225.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.236.0/22 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.240.0/23 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.243.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.247.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 92.46.0.0/15 | Route objects for it name AS9198. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.167.0/24 | No route object for it. A route object for 212.154.160.0/20 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.174.0/24 | No route object for it. A route object for 212.154.160.0/20 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.188.0/22 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.193.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.228.0/23 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.248.0/22 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.19.134.0/24 | No route object for it. A route object for 212.19.128.0/20 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.211.0/24 | No route object for it. A route object for 212.154.208.0/21 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.212.0/24 | No route object for it. A route object for 212.154.208.0/21 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.137.0/24 | No route object for it. A route object for 212.154.128.0/19 with origin AS50482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.252.0/23 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
| Route object: none | 212.154.255.0/24 | No route object for it. Add a route object with origin AS50482 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50482 whose prefix no peer sees AS50482 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.19.128.0/24 | RIPE | Valid |
| 212.19.145.0/24 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.