Network · data from 2026-11-12
AS150775 ITPL-AS-AP - iVolve Technologies Pvt. Ltd.
Registry name: ITPL-AS-AP - iVolve Technologies Pvt. Ltd., PK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS150775, 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.
| 163.52.54.0/23 | No ROA | None | 672 100% |
| 165.99.51.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 163.52.54.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 163.52.55.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 165.99.50.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 2001:df5:88c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS150775 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 3 are in fix.csv.
- ROA: none2
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 163.52.54.0/23 | No ROA covers it. Add a ROA for AS150775, maxLength 23. |
| Route object: none | 163.52.54.0/23 | No route object for it. Add a route object with origin AS150775 in the RIR database for the space. |
| ROA: none | 165.99.51.0/24 | No ROA covers it. Add a ROA for AS150775, maxLength 24. |
Route objects not announced
Every route object with origin AS150775 is announced.
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.