Network · data from 2026-11-12
AS202344 basealt LLC Basalt Svobodnoe Programnoe Obespechenie
Registry name: basealt LLC Basalt Svobodnoe Programnoe Obespechenie, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202344, 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.43.9.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.43.10.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.43.11.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a0c:88c0:1::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2a0c:88c0:2::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2a0c:88c0::/48 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS202344 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 8 are in fix.csv.
- ROA: none6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.43.9.0/24 | No ROA covers it. Add a ROA for AS202344, maxLength 24. |
| ROA: none | 193.43.10.0/24 | No ROA covers it. Add a ROA for AS202344, maxLength 24. |
| ROA: none | 193.43.11.0/24 | No ROA covers it. Add a ROA for AS202344, maxLength 24. |
| ROA: none | 2a0c:88c0:1::/48 | No ROA covers it. Add a ROA for AS202344, maxLength 48. |
| ROA: none | 2a0c:88c0:2::/48 | No ROA covers it. Add a ROA for AS202344, maxLength 48. |
| ROA: none | 2a0c:88c0::/48 | No ROA covers it. Add a ROA for AS202344, maxLength 48. |
Route objects not announced
Route objects with origin AS202344 whose prefix no peer sees AS202344 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.43.8.0/22 | RIPE | No ROA |
| 2a0c:88c0::/29 | RIPE | 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.