Network · data from 2026-11-12
AS41535 RUSONYX-AS LLC "ASTRA CLOUD"
Registry name: RUSONYX-AS LLC "ASTRA CLOUD", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41535, 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.
| 89.253.197.200/32 | Invalid: maxLength | Nonecovered by 89.253.192.0/21 | 4 1%low visibility |
| 62.113.80.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 62.213.86.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.216.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.224.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.232.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.253.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 109.120.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.120.167.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.120.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.48.236.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.32.198.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 77.221.130.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS41535 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 5 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 89.253.197.200/32 | ROA 89.253.192.0/21 AS41535 has maxLength 21; the route is a /32. Raise the maxLength, or add a ROA for 89.253.197.200/32. |
| Route object: none | 89.253.197.200/32 | No route object for it. A route object for 89.253.192.0/21 with origin AS41535 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS41535 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41535 whose prefix no peer sees AS41535 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.253.192.0/18 | RIPE | No ROA |
| 89.253.202.0/24 | RIPE | Valid |
| 89.253.203.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.