Network · data from 2026-11-12

AS132787 Micronova Network Solutions Pvt Ltd

Registry name: MNSPL-IN - Helios IT Infrasolutions Pvt Ltd, IN · PeeringDB

12IPv4 routes 66.7% 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

4No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS132787, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS132787, 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.


45.112.32.0/24	No ROA	RIR databaseAPNIC	672 100%	66
45.112.34.0/24	No ROA	RIR databaseAPNIC	672 100%	66
103.31.215.0/24	No ROA	RIR databaseAPNIC	672 100%	67
45.112.33.0/24	No ROA	RIR databaseAPNIC	671 100%	67
43.242.245.0/24	Valid	RIR databaseAPNIC	673 100%	66
43.242.246.0/24	Valid	RIR databaseAPNIC	673 100%	66
43.242.247.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.24.173.0/24	Valid	RIR databaseAPNIC	673 100%	66
43.242.244.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.24.172.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.24.174.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.24.175.0/24	Valid	RIR databaseAPNIC	672 100%	67
2402:20a0::/32	Valid	RIR databaseAPNIC	635 100%	67

AS-SET

PeeringDB's irr_as_set for AS132787: AS-MNSPL-IN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS132787 isn't in the set, or no route object for AS132787 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS132787 in it	Not covered
AS-MNSPL-IN	APNIC	8	1	167	Yes	0

Name

Database

ASNs

Sets

Route objects

AS132787 in it

Not covered

AS-MNSPL-IN

APNIC

167

Yes

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: none4

Change	Prefix or set	Detail	Full-table peers
ROA: none	45.112.32.0/24	No ROA covers it. Add a ROA for AS132787, maxLength 24.	672 of 673
ROA: none	45.112.34.0/24	No ROA covers it. Add a ROA for AS132787, maxLength 24.	672 of 673
ROA: none	103.31.215.0/24	No ROA covers it. Add a ROA for AS132787, maxLength 24.	672 of 673
ROA: none	45.112.33.0/24	No ROA covers it. Add a ROA for AS132787, maxLength 24.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

45.112.32.0/24

No ROA covers it. Add a ROA for AS132787, maxLength 24.

672 of 673

ROA: none

45.112.34.0/24

No ROA covers it. Add a ROA for AS132787, maxLength 24.

672 of 673

ROA: none

103.31.215.0/24

No ROA covers it. Add a ROA for AS132787, maxLength 24.

672 of 673

ROA: none

45.112.33.0/24

No ROA covers it. Add a ROA for AS132787, maxLength 24.

671 of 673

Route objects not announced

Every route object with origin AS132787 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.