Network · data from 2026-11-12
AS29061 Saimanet Telecomunications
Registry name: SAIMANET-AS CJSC SAIMA TELECOM, KG · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29061, 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.
| 217.29.31.0/24 | Valid | Nonecovered by 217.29.24.0/21 | 671 100% |
| 92.62.64.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.64.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.65.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.66.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.68.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.69.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.70.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.71.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.72.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.72.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.73.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.74.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.75.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.62.76.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.72.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.72.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.76.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.80.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.88.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.92.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.92.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.93.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.94.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 95.87.95.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.53.228.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.53.228.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.53.229.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.53.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.53.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.16.0/20 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.16.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.16.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.18.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.19.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.20.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.22.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.23.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.24.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.24.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.25.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.26.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.27.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.29.29.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS29061's PeeringDB record names no 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 11 are in fix.csv.
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.29.31.0/24 | No route object for it. A route object for 217.29.24.0/21 with origin AS29061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29061 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS29061 whose prefix no peer sees AS29061 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.62.64.0/24 | RIPE | Valid |
| 92.62.66.0/24 | RIPE | Valid |
| 92.62.67.0/24 | RIPE | Valid |
| 92.62.76.0/24 | RIPE | Valid |
| 92.62.77.0/24 | RIPE | Valid |
| 92.62.78.0/24 | RIPE | Valid |
| 92.62.79.0/24 | RIPE | Valid |
| 95.87.72.0/24 | RIPE | Valid |
| 95.87.86.0/23 | RIPE | Valid |
| 2a02:820::/32 | 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.