bgpreport

Network · data from 2026-11-12

AS9796 WIPRO - Internet Service Providers

Registry name: WIPRO - Internet Service Providers, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9796, 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.
202.177.128.0/23 No ROA RIR databaseAPNIC 673 100% 66
202.177.129.0/24 No ROA RIR databaseAPNIC 673 100% 67
202.177.130.0/23 No ROA RIR databaseAPNIC 673 100% 66
202.177.130.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.177.132.0/24 No ROA RIR databaseAPNIC 673 100% 66
202.177.136.0/23 No ROA RIR databaseAPNIC 673 100% 66
202.177.136.0/24 No ROA RIR databaseAPNIC 673 100% 67
202.177.138.0/23 No ROA RIR databaseAPNIC 673 100% 66
202.177.138.0/24 No ROA RIR databaseAPNIC 673 100% 67

AS-SET

AS9796 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 40 are in fix.csv.

  • ROA: none9
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none202.177.128.0/23No ROA covers it. Add a ROA for AS9796, maxLength 23.673 of 673
ROA: none202.177.129.0/24No ROA covers it. Add a ROA for AS9796, maxLength 24.673 of 673
ROA: none202.177.130.0/23No ROA covers it. Add a ROA for AS9796, maxLength 23.673 of 673
ROA: none202.177.130.0/24No ROA covers it. Add a ROA for AS9796, maxLength 24.673 of 673
ROA: none202.177.132.0/24No ROA covers it. Add a ROA for AS9796, maxLength 24.673 of 673
ROA: none202.177.136.0/23No ROA covers it. Add a ROA for AS9796, maxLength 23.673 of 673
ROA: none202.177.136.0/24No ROA covers it. Add a ROA for AS9796, maxLength 24.673 of 673
ROA: none202.177.138.0/23No ROA covers it. Add a ROA for AS9796, maxLength 23.673 of 673
ROA: none202.177.138.0/24No ROA covers it. Add a ROA for AS9796, maxLength 24.673 of 673

Route objects not announced

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

196.15.16.0/20APNICNo ROA
202.177.128.0/20APNICNo ROA
202.177.128.0/21APNICNo ROA
202.177.128.0/22APNICNo ROA
202.177.128.0/24APNICNo ROA
202.177.131.0/24APNICNo ROA
202.177.132.0/22APNICNo ROA
202.177.132.0/23APNICNo ROA
202.177.133.0/24APNICNo ROA
202.177.134.0/23APNICNo ROA
202.177.134.0/24APNICNo ROA
202.177.135.0/24APNICNo ROA
202.177.136.0/21APNICNo ROA
202.177.136.0/22APNICNo ROA
202.177.137.0/24APNICNo ROA
202.177.139.0/24APNICNo ROA
202.177.140.0/22APNICNo ROA
202.177.140.0/23APNICNo ROA
202.177.140.0/24APNICNo ROA
202.177.141.0/24APNICNo ROA
202.177.142.0/23APNICNo ROA
202.177.142.0/24APNICNo ROA
202.177.143.0/24APNICNo ROA
210.18.6.0/23RADBNo ROA
210.18.84.0/24APNICInvalid: origin
221.134.0.0/18APNICNo ROA
221.134.18.0/24APNICInvalid: origin
221.134.72.0/24APNICInvalid: origin
221.134.91.0/24APNICInvalid: origin
221.134.127.0/24APNICInvalid: origin
221.134.157.0/24APNICInvalid: origin

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.