Network · data from 2026-11-12
AS44653 HALYKBANK-AS JSC People's Savings Bank Kazakhstan
Registry name: HALYKBANK-AS JSC People's Savings Bank Kazakhstan, KZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44653, 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.145.224/27 | Invalid: origin | None | 1 0%low visibility |
| 193.93.56.0/24 | No ROA | None | 1 0%low visibility |
| 193.93.57.0/24 | No ROA | None | 1 0%low visibility |
| 193.93.58.0/24 | No ROA | None | 1 0%low visibility |
| 195.200.74.0/24 | No ROA | Nonecovered by 195.200.74.0/23 | 1 0%low visibility |
| 195.200.75.0/24 | No ROA | Nonecovered by 195.200.74.0/23 | 1 0%low visibility |
| 195.200.74.0/23 | No ROA | RIR databaseRADB, RIPE | 669 99% |
| 212.19.135.0/24 | Valid | Other origin only | 673 100% |
| 212.19.137.0/24 | Valid | Other origin only | 673 100% |
AS-SET
AS44653 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 15 are in fix.csv.
- ROA: origin1
- ROA: none6
- Route object: none8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 212.154.145.224/27 | ROAs covering it name AS9198, AS50482, not AS44653. If AS44653 should announce it, add a ROA for AS44653. |
| Route object: none | 212.154.145.224/27 | No route object for it. Add a route object with origin AS44653 in the RIR database for the space. |
| ROA: none | 193.93.56.0/24 | No ROA covers it. Add a ROA for AS44653, maxLength 24. |
| Route object: none | 193.93.56.0/24 | No route object for it. Add a route object with origin AS44653 in the RIR database for the space. |
| ROA: none | 193.93.57.0/24 | No ROA covers it. Add a ROA for AS44653, maxLength 24. |
| Route object: none | 193.93.57.0/24 | No route object for it. Add a route object with origin AS44653 in the RIR database for the space. |
| ROA: none | 193.93.58.0/24 | No ROA covers it. Add a ROA for AS44653, maxLength 24. |
| Route object: none | 193.93.58.0/24 | No route object for it. Add a route object with origin AS44653 in the RIR database for the space. |
| ROA: none | 195.200.74.0/24 | No ROA covers it. Add a ROA for AS44653, maxLength 24. |
| Route object: none | 195.200.74.0/24 | No route object for it. A route object for 195.200.74.0/23 with origin AS44653 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44653 in the RIR database for the space. |
| ROA: none | 195.200.75.0/24 | No ROA covers it. Add a ROA for AS44653, maxLength 24. |
| Route object: none | 195.200.75.0/24 | No route object for it. A route object for 195.200.74.0/23 with origin AS44653 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44653 in the RIR database for the space. |
| ROA: none | 195.200.74.0/23 | No ROA covers it. Add a ROA for AS44653, maxLength 23. |
| Route object: none | 212.19.135.0/24 | Route objects for it name AS9198. Add a route object with origin AS44653 in the RIR database for the space. |
| Route object: none | 212.19.137.0/24 | Route objects for it name AS9198. Add a route object with origin AS44653 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS44653 is announced.
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.