bgpreport

Network · data from 2026-11-12

AS135846 Nirav Infotech

Registry name: JOISTER-NIRAV-AS - Nirav Infotech, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135846, 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.51.138.0/24 No ROA RIR databaseAPNIC 671 100% 67
103.51.136.0/24 Valid RIR databaseAPNIC 671 100% 67
103.51.137.0/24 Valid RIR databaseAPNIC 671 100% 67
103.51.139.0/24 Valid RIR databaseAPNIC 671 100% 67
45.124.140.0/24 Valid RIR databaseAPNIC 670 100% 67
45.124.141.0/24 Valid RIR databaseAPNIC 670 100% 67
45.124.142.0/24 Valid RIR databaseAPNIC 670 100% 67
45.124.143.0/24 Valid RIR databaseAPNIC 670 100% 67
2001:df5:d280::/48 Valid RIR databaseAPNIC 635 100% 67

AS-SET

AS135846'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 4 are in fix.csv.

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none103.51.138.0/24No ROA covers it. Add a ROA for AS135846, maxLength 24.671 of 673

Route objects not announced

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

45.124.140.0/22RADBNo ROA
103.51.136.0/22RADBNo ROA
103.217.131.0/24APNICValid

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.