bgpreport

Network · data from 2026-11-12

AS146871 MRVPL-AS-IN - MANAV RACHNA VIDYANATARIKSHA PRIVATE LIMITED

Registry name: MRVPL-AS-IN - MANAV RACHNA VIDYANATARIKSHA PRIVATE LIMITED, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS146871, 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.43.207.0/24 Invalid: origin Other origin only 1 0%low visibility 1
79.182.24.0/24 Invalid: origin None 1 0%low visibility 1
82.21.57.0/24 Invalid: origin Other origin only 1 0%low visibility 1
104.166.69.0/24 Invalid: origin Other origin only 1 0%low visibility 1
174.140.250.0/24 Invalid: origin Other origin only 1 0%low visibility 1
213.145.70.0/24 Invalid: origin Other origin only 1 0%low visibility 1
23.95.83.0/24 No ROA Other origin only 2 0%low visibility 2
194.33.182.0/24 No ROA Other origin only 2 0%low visibility 2

AS-SET

AS146871 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 16 are in fix.csv.

  • ROA: origin6
  • ROA: none2
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: origin45.43.207.0/24ROAs covering it name AS30088, not AS146871. If AS146871 should announce it, add a ROA for AS146871.1 of 673
Route object: none45.43.207.0/24Route objects for it name AS30088. Add a route object with origin AS146871 in the RIR database for the space.1 of 673
ROA: origin79.182.24.0/24ROAs covering it name AS834, not AS146871. If AS146871 should announce it, add a ROA for AS146871.1 of 673
Route object: none79.182.24.0/24No route object for it. Add a route object with origin AS146871 in the RIR database for the space.1 of 673
ROA: origin82.21.57.0/24ROAs covering it name AS214647, not AS146871. If AS146871 should announce it, add a ROA for AS146871.1 of 673
Route object: none82.21.57.0/24Route objects for it name AS214647. Add a route object with origin AS146871 in the RIR database for the space.1 of 673
ROA: origin104.166.69.0/24ROAs covering it name AS30088, not AS146871. If AS146871 should announce it, add a ROA for AS146871.1 of 673
Route object: none104.166.69.0/24Route objects for it name AS30088. Add a route object with origin AS146871 in the RIR database for the space.1 of 673
ROA: origin174.140.250.0/24ROAs covering it name AS834, AS17252, not AS146871. If AS146871 should announce it, add a ROA for AS146871.1 of 673
Route object: none174.140.250.0/24Route objects for it name AS834. Add a route object with origin AS146871 in the RIR database for the space.1 of 673
ROA: origin213.145.70.0/24ROAs covering it name AS834, not AS146871. If AS146871 should announce it, add a ROA for AS146871.1 of 673
Route object: none213.145.70.0/24Route objects for it name AS834. Add a route object with origin AS146871 in the RIR database for the space.1 of 673
ROA: none23.95.83.0/24No ROA covers it. Add a ROA for AS146871, maxLength 24.2 of 673
Route object: none23.95.83.0/24Route objects for it name AS834. Add a route object with origin AS146871 in the RIR database for the space.2 of 673
ROA: none194.33.182.0/24No ROA covers it. Add a ROA for AS146871, maxLength 24.2 of 673
Route object: none194.33.182.0/24Route objects for it name AS834. Add a route object with origin AS146871 in the RIR database for the space.2 of 673

Route objects not announced

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