Network · data from 2026-11-12
AS21051 NIVAL-AS ASTRUM LLC
Registry name: NIVAL-AS ASTRUM LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21051, 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.
| 92.38.246.0/24 | No ROA | Nonecovered by 92.38.246.0/23 | 672 100% |
| 92.38.247.0/24 | No ROA | Nonecovered by 92.38.246.0/23 | 672 100% |
| 208.87.93.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 2 0%low visibility |
| 92.38.244.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.16.8.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 195.211.128.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 92.38.244.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 185.16.9.0/24 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 185.16.10.0/24 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 185.16.11.0/24 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 2a05:c3c0::/32 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS21051 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 21 are in fix.csv.
- ROA: none10
- Route object: none2
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 92.38.246.0/24 | No ROA covers it. Add a ROA for AS21051, maxLength 24. |
| Route object: none | 92.38.246.0/24 | No route object for it. A route object for 92.38.246.0/23 with origin AS21051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21051 in the RIR database for the space. |
| ROA: none | 92.38.247.0/24 | No ROA covers it. Add a ROA for AS21051, maxLength 24. |
| Route object: none | 92.38.247.0/24 | No route object for it. A route object for 92.38.246.0/23 with origin AS21051 covers it (filters allowing more-specifics accept it). Add a route object with origin AS21051 in the RIR database for the space. |
| ROA: none | 208.87.93.0/24 | No ROA covers it. Add a ROA for AS21051, maxLength 24. |
| Route object: RIR | 208.87.93.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 92.38.244.0/22 | No ROA covers it. Add a ROA for AS21051, maxLength 22. |
| ROA: none | 185.16.8.0/22 | No ROA covers it. Add a ROA for AS21051, maxLength 22. |
| ROA: none | 195.211.128.0/22 | No ROA covers it. Add a ROA for AS21051, maxLength 22. |
| ROA: none | 92.38.244.0/23 | No ROA covers it. Add a ROA for AS21051, maxLength 23. |
| ROA: none | 185.16.9.0/24 | No ROA covers it. Add a ROA for AS21051, maxLength 24. |
| ROA: none | 185.16.10.0/24 | No ROA covers it. Add a ROA for AS21051, maxLength 24. |
| ROA: none | 185.16.11.0/24 | No ROA covers it. Add a ROA for AS21051, maxLength 24. |
Route objects not announced
Route objects with origin AS21051 whose prefix no peer sees AS21051 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.38.246.0/23 | RIPE | No ROA |
| 185.16.8.0/23 | RIPE | No ROA |
| 195.211.128.0/23 | RIPE | No ROA |
| 195.211.128.0/24 | RIPE | No ROA |
| 195.211.129.0/24 | RIPE | No ROA |
| 195.211.130.0/23 | RIPE | No ROA |
| 208.87.94.0/24 | RIPE-NONAUTH | No ROA |
| 208.87.95.0/24 | RIPE-NONAUTH | No ROA |
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.