Network · data from 2026-11-12
AS135383 CLOUDWARE-AS-AP - Cloudware Technologies Private Limited
Registry name: CLOUDWARE-AS-AP - Cloudware Technologies Private Limited, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS135383, 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.
| 103.255.64.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 103.255.65.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
AS-SET
AS135383 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 19 are in fix.csv.
- ROA: none2
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.255.64.0/24 | No ROA covers it. Add a ROA for AS135383, maxLength 24. |
| ROA: none | 103.255.65.0/24 | No ROA covers it. Add a ROA for AS135383, maxLength 24. |
Route objects not announced
Route objects with origin AS135383 whose prefix no peer sees AS135383 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:df2:e7c0::/48 | APNIC | No ROA |
| 2a0e:b107:90::/44 | RIPE | No ROA |
| 2a0e:b107:90::/48 | RIPE | No ROA |
| 2a0e:b107:91::/48 | RIPE | No ROA |
| 2a0e:b107:92::/48 | RIPE | No ROA |
| 2a0e:b107:93::/48 | RIPE | No ROA |
| 2a0e:b107:94::/48 | RIPE | No ROA |
| 2a0e:b107:95::/48 | RIPE | No ROA |
| 2a0e:b107:96::/48 | RIPE | No ROA |
| 2a0e:b107:97::/48 | RIPE | No ROA |
| 2a0e:b107:98::/48 | RIPE | No ROA |
| 2a0e:b107:99::/48 | RIPE | No ROA |
| 2a0e:b107:9a::/48 | RIPE | No ROA |
| 2a0e:b107:9b::/48 | RIPE | No ROA |
| 2a0e:b107:9c::/48 | RIPE | No ROA |
| 2a0e:b107:9d::/48 | RIPE | No ROA |
| 2a0e:b107:9e::/48 | 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.