Network · data from 2026-11-12
AS21294 CLOUDSYS TELECOM
Registry name: IDILIS CLOUDSYS TELECOM SRL, RO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS21294, 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.
| 80.97.0.0/20 | No ROA | RIR databaseRIPE | 670 100% |
| 84.239.19.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.20.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.21.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.22.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.23.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.24.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.26.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 84.239.53.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.102.220.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.156.85.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.156.99.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS21294'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 3 are in fix.csv.
- ROA: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 80.97.0.0/20 | No ROA covers it. Add a ROA for AS21294, maxLength 20. |
Route objects not announced
Route objects with origin AS21294 whose prefix no peer sees AS21294 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.97.12.0/24 | RIPE | No ROA |
| 2a02:2160:6000::/36 | 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.