bgpreport

Network · data from 2026-11-12

AS9430 STPI-NOIDA - Software Technology Parks of India,Block-IV

Registry name: STPI-NOIDA - Software Technology Parks of India,Block-IV, IN · not in PeeringDB

35IPv4 routes 25.7% RPKI valid · 88.6% with a route object
4IPv6 routes 0.0% RPKI valid · 75.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
29No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
65Route objects not announced registered with origin AS9430, seen from no peer

Announced routes

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

164.164.190.0/24 Invalid: origin RIR databaseAPNIC 137 20% 53
103.35.120.0/24 No ROA Other origin only 673 100% 67
103.35.121.0/24 No ROA Other origin only 673 100% 67
203.190.131.0/24 No ROA Nonecovered by 203.190.130.0/23 672 100% 67
103.60.156.0/24 No ROA Nonecovered by 103.60.156.0/22 670 100% 66
2402:ef13:1::/48 No ROA Nonecovered by 2402:ef13::/32 636 100% 69
203.193.179.0/24 No ROA Other IRR onlyRADB 673 100% 66
203.190.132.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.190.133.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.100.66.0/24 No ROA RIR databaseAPNIC 673 100% 67
203.100.68.0/24 No ROA RIR databaseAPNIC 673 100% 67
203.100.70.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
203.100.78.0/24 No ROA RIR databaseAPNIC 673 100% 66
203.100.79.0/24 No ROA RIR databaseAPNIC 673 100% 66
203.129.208.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 66
203.129.220.0/24 No ROA RIR databaseAPNIC 673 100% 66
203.190.134.0/24 No ROA RIR databaseAPNIC 673 100% 66
203.190.139.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 66
203.190.153.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 66
203.190.154.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 66
203.193.132.0/24 No ROA RIR databaseAPNIC 673 100% 66
203.193.166.0/24 No ROA RIR databaseAPNIC 673 100% 66
203.193.170.0/24 No ROA RIR databaseAPNIC 673 100% 66
203.190.128.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
203.190.135.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
203.190.136.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 67
203.190.150.0/24 No ROA RIR databaseAPNIC 669 99% 67
2402:ef09::/32 No ROA RIR databaseAPNIC 636 100% 70
2402:ef0f::/32 No ROA RIR databaseAPNIC 636 100% 70
2402:ef15::/32 No ROA RIR databaseAPNIC 636 100% 69
103.171.96.0/24 Valid RIR databaseAPNIC 673 100% 66
161.248.26.0/24 Valid RIR databaseAPNIC 673 100% 67
164.164.32.0/24 Valid RIR databaseAPNIC 673 100% 67
164.164.126.0/24 Valid RIR databaseAPNIC 673 100% 67
164.164.127.0/24 Valid RIR databaseAPNIC 673 100% 67
164.164.184.0/24 Valid RIR databaseAPNIC 673 100% 66
164.164.187.0/24 Valid RIR databaseAPNIC 673 100% 67
203.190.144.0/24 Valid RIR databaseAPNIC 673 100% 66
164.164.192.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS9430 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 103 are in fix.csv.

  • ROA: origin1
  • ROA: none29
  • Route object: none5
  • Route object: RIR3
  • Route object: not announced65
ChangePrefix or setDetailFull-table peers
ROA: origin164.164.190.0/24ROAs covering it name AS7633, not AS9430. If AS9430 should announce it, add a ROA for AS9430.137 of 673
ROA: none103.35.120.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
Route object: none103.35.120.0/24Route objects for it name AS38546, AS134255. Add a route object with origin AS9430 in the RIR database for the space.673 of 673
ROA: none103.35.121.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
Route object: none103.35.121.0/24Route objects for it name AS38546, AS134255. Add a route object with origin AS9430 in the RIR database for the space.673 of 673
ROA: none203.190.131.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.672 of 673
Route object: none203.190.131.0/24No route object for it. A route object for 203.190.130.0/23 with origin AS9430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9430 in the RIR database for the space.672 of 673
ROA: none103.60.156.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.670 of 673
Route object: none103.60.156.0/24No route object for it. A route object for 103.60.156.0/22 with origin AS9430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9430 in the RIR database for the space.670 of 673
ROA: none2402:ef13:1::/48No ROA covers it. Add a ROA for AS9430, maxLength 48.636 of 636
Route object: none2402:ef13:1::/48No route object for it. A route object for 2402:ef13::/32 with origin AS9430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9430 in the RIR database for the space.636 of 636
ROA: none203.193.179.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
Route object: RIR203.193.179.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.190.132.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.672 of 673
Route object: RIR203.190.132.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.190.133.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.672 of 673
Route object: RIR203.190.133.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.100.66.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.100.68.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.100.70.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.100.78.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.100.79.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.129.208.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.129.220.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.190.134.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.190.139.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.190.153.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.190.154.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.193.132.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.193.166.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.193.170.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.673 of 673
ROA: none203.190.128.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.672 of 673
ROA: none203.190.135.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.672 of 673
ROA: none203.190.136.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.672 of 673
ROA: none203.190.150.0/24No ROA covers it. Add a ROA for AS9430, maxLength 24.669 of 673
ROA: none2402:ef09::/32No ROA covers it. Add a ROA for AS9430, maxLength 32.636 of 636
ROA: none2402:ef0f::/32No ROA covers it. Add a ROA for AS9430, maxLength 32.636 of 636
ROA: none2402:ef15::/32No ROA covers it. Add a ROA for AS9430, maxLength 32.636 of 636

Route objects not announced

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

45.120.92.0/22APNICNo ROA
103.60.156.0/22APNICNo ROA
103.171.96.0/23APNICValid
103.171.97.0/24APNICValid
117.103.8.0/21NTTCOM, RADBNo ROA
157.15.159.0/24APNICValid
164.164.123.0/24APNICValid
164.164.124.0/24APNICValid
202.41.4.0/24APNIC, REACHNo ROA
202.41.5.0/24APNIC, REACHNo ROA
202.41.10.0/24REACHInvalid: origin
202.67.32.0/20NTTCOM, RADBNo ROA
202.93.224.0/20NTTCOM, RADBNo ROA
202.93.240.0/21NTTCOM, RADBNo ROA
202.123.224.0/20NTTCOM, RADBNo ROA
202.142.7.0/24RADBNo ROA
202.148.0.0/19NTTCOM, RADBNo ROA
202.159.0.0/17NTTCOM, RADBNo ROA
202.160.254.0/24NTTCOM, RADBNo ROA
202.162.48.0/20REACHNo ROA
202.180.48.0/21RADBNo ROA
203.78.128.0/24REACHInvalid: origin
203.100.64.0/24APNICNo ROA
203.100.65.0/24APNICNo ROA
203.100.67.0/24APNICNo ROA
203.100.69.0/24APNICNo ROA
203.100.71.0/24APNICNo ROA
203.100.72.0/24REACHNo ROA
203.100.75.0/24APNIC, RADBNo ROA
203.100.76.0/24APNIC, RADBNo ROA
203.129.192.0/24APNIC, RADBNo ROA
203.129.200.0/24REACHNo ROA
203.129.201.0/24REACHNo ROA
203.190.128.0/18REACHNo ROA
203.190.128.0/19APNICNo ROA
203.190.128.0/20APNICNo ROA
203.190.128.0/23APNICNo ROA
203.190.129.0/24APNICNo ROA
203.190.130.0/23APNICNo ROA
203.190.132.0/23APNICNo ROA
203.190.136.0/22APNICNo ROA
203.190.137.0/24APNICNo ROA
203.190.138.0/24APNICNo ROA
203.190.140.0/24APNICNo ROA
203.190.141.0/24APNICNo ROA
203.190.142.0/24APNIC, RADBNo ROA
203.190.143.0/24APNICNo ROA
203.190.145.0/24APNICNo ROA
203.190.148.0/23APNICNo ROA
203.190.155.0/24APNIC, RADBValid
203.190.156.0/24APNIC, RADBValid
203.190.157.0/24APNIC, RADBValid
203.190.158.0/24APNIC, RADBValid
203.190.159.0/24APNICValid
203.193.143.0/24REACHNo ROA
203.201.160.0/20NTTCOM, RADBNo ROA
2402:ef00::/26APNICNo ROA
2402:ef00::/32APNICNo ROA
2402:ef01::/32APNICNo ROA
2402:ef01:2::/48APNICValid
2402:ef01:3::/48APNICValid
2402:ef10::/32APNICNo ROA
2402:ef11::/32APNICNo ROA
2402:ef13::/32APNICNo ROA
2402:ef16::/32APNICValid

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.