bgpreport

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

5IPv4 routes 60.0% RPKI valid · 80.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS150775, seen from no peer

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% 67
165.99.51.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
163.52.54.0/24 Valid RIR databaseAPNIC 673 100% 67
163.52.55.0/24 Valid RIR databaseAPNIC 673 100% 67
165.99.50.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
2001:df5:88c0::/48 Valid RIR databaseAPNIC 636 100% 70

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
ChangePrefix or setDetailFull-table peers
ROA: none163.52.54.0/23No ROA covers it. Add a ROA for AS150775, maxLength 23.672 of 673
Route object: none163.52.54.0/23No route object for it. Add a route object with origin AS150775 in the RIR database for the space.672 of 673
ROA: none165.99.51.0/24No ROA covers it. Add a ROA for AS150775, maxLength 24.673 of 673

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.