Network · data from 2026-11-12
AS153393 RACKVOLT-AS-AP - RACKVOLT CLOUD SOLUTIONS PRIVATE LIMITED
Registry name: RACKVOLT-AS-AP - RACKVOLT CLOUD SOLUTIONS PRIVATE LIMITED, IN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS153393, 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.202.61.0/24 | Invalid: origin | None | 201 30% |
| 103.202.153.0/24 | Invalid: origin | None | 201 30% |
| 92.118.235.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 165.140.166.0/24 | Valid | RIR databaseARIN | 673 100% |
| 185.223.78.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 192.6.160.0/24 | Valid | RIR databaseARIN, RADB | 673 100% |
| 45.158.56.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 160.191.182.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.191.183.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.32.25.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 2401:d4e0:1::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS153393 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 6 are in fix.csv.
- ROA: origin2
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.202.61.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS153393 should announce it, add a ROA for AS153393. |
| Route object: none | 103.202.61.0/24 | No route object for it. Add a route object with origin AS153393 in the RIR database for the space. |
| ROA: origin | 103.202.153.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS153393 should announce it, add a ROA for AS153393. |
| Route object: none | 103.202.153.0/24 | No route object for it. Add a route object with origin AS153393 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS153393 whose prefix no peer sees AS153393 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2401:d4e0::/48 | APNIC | Valid |
| 2401:d4e0:2::/48 | APNIC | 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.