bgpreport

Network · data from 2026-11-12

AS149021 Inara Technologies Private Limited

Registry name: INARA-AS-AP - Inara Technologies Private Limited, PK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149021, 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.176.204.0/23 Valid RIR databaseAPNIC 672 100% 66
103.176.204.0/24 Valid RIR databaseAPNIC 672 100% 66
103.176.205.0/24 Valid RIR databaseAPNIC 672 100% 66
2401:43e0:1::/48 Valid RIR databaseAPNIC 635 100% 69
2401:43e0::/32 Valid RIR databaseAPNIC 634 100% 69
2401:43e0:2::/48 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS149021'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 15 are in fix.csv.

  • Route object: not announced15

Route objects not announced

Route objects with origin AS149021 whose prefix no peer sees AS149021 announce. Many are kept on purpose (backup routes, space announced only in some places).

2401:43e0::/48APNICValid
2401:43e0:2::/47APNICValid
2401:43e0:4::/46APNICValid
2401:43e0:10::/44APNICValid
2401:43e0:20::/43APNICValid
2401:43e0:40::/42APNICValid
2401:43e0:80::/41APNICValid
2401:43e0:100::/40APNICValid
2401:43e0:200::/39APNICValid
2401:43e0:400::/38APNICValid
2401:43e0:800::/37APNICValid
2401:43e0:1000::/36APNICValid
2401:43e0:2000::/35APNICValid
2401:43e0:4000::/34APNICValid
2401:43e0:8000::/33APNICValid

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.