Network · data from 2026-11-12
AS208795 YANDEXCLOUDKZ "Cloud Services Kazakhstan" LLP
Registry name: YANDEXCLOUDKZ "Cloud Services Kazakhstan" LLP, KZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208795, 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.
| 5.35.104.0/24 | Valid | Nonecovered by 5.35.104.0/21 | 673 100% |
| 5.35.105.0/24 | Valid | Nonecovered by 5.35.104.0/21 | 673 100% |
| 5.35.107.0/24 | Valid | Nonecovered by 5.35.104.0/21 | 673 100% |
| 5.35.108.0/24 | Valid | Nonecovered by 5.35.104.0/21 | 673 100% |
| 94.131.176.0/21 | Valid | Nonecovered by 94.131.176.0/20 | 673 100% |
| 94.131.184.0/22 | Valid | Nonecovered by 94.131.176.0/20 | 673 100% |
| 185.32.84.0/24 | Valid | Nonecovered by 185.32.84.0/22 | 673 100% |
| 185.32.85.0/24 | Valid | Nonecovered by 185.32.84.0/22 | 673 100% |
| 5.35.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.32.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.135.172.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2a07:aa40:20::/44 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS208795 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 17 are in fix.csv.
- Route object: none8
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.35.104.0/24 | No route object for it. A route object for 5.35.104.0/21 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
| Route object: none | 5.35.105.0/24 | No route object for it. A route object for 5.35.104.0/21 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
| Route object: none | 5.35.107.0/24 | No route object for it. A route object for 5.35.104.0/21 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
| Route object: none | 5.35.108.0/24 | No route object for it. A route object for 5.35.104.0/21 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
| Route object: none | 94.131.176.0/21 | No route object for it. A route object for 94.131.176.0/20 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
| Route object: none | 94.131.184.0/22 | No route object for it. A route object for 94.131.176.0/20 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
| Route object: none | 185.32.84.0/24 | No route object for it. A route object for 185.32.84.0/22 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
| Route object: none | 185.32.85.0/24 | No route object for it. A route object for 185.32.84.0/22 with origin AS208795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208795 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS208795 whose prefix no peer sees AS208795 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.131.176.0/20 | RIPE | Valid |
| 94.131.190.0/24 | RIPE | Valid |
| 94.131.191.0/24 | RIPE | Valid |
| 2a07:aa40::/44 | RIPE | Valid |
| 2a07:aa40:10::/44 | RIPE | Valid |
| 2a07:aa40:30::/44 | RIPE | Valid |
| 2a07:aa40:40::/48 | RIPE | Valid |
| 2a07:aa40:41::/48 | RIPE | Valid |
| 2a07:aa40:100::/40 | 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.