Network · data from 2026-11-12
AS3218 COSMOS-3218-AS Federal State Budgetary Institution of Science "Space Research Institute of the Russian Academy of Sciences".
Registry name: COSMOS-3218-AS Federal State Budgetary Institution of Science "Space Research Institute of the Russian Academy of Sciences"., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS3218, 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.
| 193.232.23.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 193.232.208.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 194.85.209.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 194.85.213.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 62.61.16.0/20 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.3.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.4.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.6.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.9.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.10.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.12.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.28.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.31.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.192.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.193.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.194.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.195.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.196.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.197.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.207.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.218.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.232.219.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.61.16.0/21 | Valid | RIR databaseRIPE | 669 99% |
| 62.61.24.0/21 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS3218 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 25 are in fix.csv.
- ROA: none4
- Route object: not announced21
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.232.23.0/24 | No ROA covers it. Add a ROA for AS3218, maxLength 24. |
| ROA: none | 193.232.208.0/24 | No ROA covers it. Add a ROA for AS3218, maxLength 24. |
| ROA: none | 194.85.209.0/24 | No ROA covers it. Add a ROA for AS3218, maxLength 24. |
| ROA: none | 194.85.213.0/24 | No ROA covers it. Add a ROA for AS3218, maxLength 24. |
Route objects not announced
Route objects with origin AS3218 whose prefix no peer sees AS3218 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.61.16.0/24 | RIPE | Invalid: maxLength |
| 62.61.17.0/24 | RIPE | Invalid: maxLength |
| 62.61.18.0/24 | RIPE | Invalid: maxLength |
| 62.61.19.0/24 | RIPE | Invalid: maxLength |
| 62.61.20.0/24 | RIPE | Invalid: maxLength |
| 62.61.21.0/24 | RIPE | Invalid: maxLength |
| 62.61.22.0/24 | RIPE | Invalid: maxLength |
| 62.61.23.0/24 | RIPE | Invalid: maxLength |
| 62.61.24.0/24 | RIPE | Invalid: maxLength |
| 62.61.25.0/24 | RIPE | Invalid: maxLength |
| 62.61.26.0/24 | RIPE | Invalid: maxLength |
| 62.61.27.0/24 | RIPE | Valid |
| 62.61.28.0/24 | RIPE | Invalid: maxLength |
| 62.61.29.0/24 | RIPE | Invalid: maxLength |
| 62.61.30.0/24 | RIPE | Valid |
| 62.61.31.0/24 | RIPE | Invalid: maxLength |
| 194.85.223.0/24 | RIPE | No ROA |
| 2a0c:6d00::/32 | RIPE | No ROA |
| 2a0c:6d00:61::/48 | RIPE | Valid |
| 2a0c:6d00:85::/48 | RIPE | Valid |
| 2a0c:6d00:232::/48 | 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.