bgpreport

Network · data from 2026-11-12

AS38529 RELIANCE-RIL-AS-AP - Reliance Industries Limited WAN Backbone Interface with ISPs in India

Registry name: RELIANCE-RIL-AS-AP - Reliance Industries Limited WAN Backbone Interface with ISPs in India, IN · not in PeeringDB

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

Announced routes

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

2402:8e00:2::/48 No ROA Nonecovered by 2402:8e00::/35 636 100% 69
2402:8e00::/32 No ROA Other IRR onlyRADB 636 100% 69
49.40.59.0/24 Valid RIR databaseAPNIC 673 100% 67
116.50.64.0/18 Valid RIR databaseAPNIC 673 100% 67
116.50.74.0/24 Valid RIR databaseAPNIC 673 100% 67
116.50.76.0/24 Valid RIR databaseAPNIC 673 100% 67
116.50.88.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
116.50.91.0/24 Valid RIR databaseAPNIC 673 100% 67
116.50.94.0/24 Valid RIR databaseAPNIC 673 100% 67
116.50.64.0/19 Valid RIR databaseAPNIC, RADB 672 100% 67
116.50.66.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
116.50.67.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
116.50.70.0/24 Valid RIR databaseAPNIC 672 100% 67
116.50.78.0/23 Valid RIR databaseAPNIC, RADB 672 100% 67
116.50.81.0/24 Valid RIR databaseAPNIC 672 100% 67
116.50.83.0/24 Valid RIR databaseAPNIC 672 100% 67
116.50.84.0/24 Valid RIR databaseAPNIC 672 100% 67
116.50.85.0/24 Valid RIR databaseAPNIC 672 100% 67
116.50.96.0/23 Valid RIR databaseAPNIC 672 100% 67
116.50.113.0/24 Valid RIR databaseAPNIC 672 100% 67
116.50.121.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS38529 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 116 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced112
ChangePrefix or setDetailFull-table peers
ROA: none2402:8e00:2::/48No ROA covers it. Add a ROA for AS38529, maxLength 48.636 of 636
Route object: none2402:8e00:2::/48No route object for it. A route object for 2402:8e00::/35 with origin AS38529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38529 in the RIR database for the space.636 of 636
ROA: none2402:8e00::/32No ROA covers it. Add a ROA for AS38529, maxLength 32.636 of 636
Route object: RIR2402:8e00::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

116.50.64.0/20APNICValid
116.50.64.0/21APNICValid
116.50.64.0/22APNICValid
116.50.64.0/23APNICValid
116.50.64.0/24APNIC, RADBValid
116.50.65.0/24APNICValid
116.50.66.0/23APNICValid
116.50.68.0/22APNICValid
116.50.68.0/23APNICValid
116.50.68.0/24APNICValid
116.50.69.0/24APNICValid
116.50.70.0/23APNICValid
116.50.71.0/24APNICValid
116.50.72.0/21APNICValid
116.50.72.0/22APNICValid
116.50.72.0/23APNICValid
116.50.72.0/24APNICValid
116.50.73.0/24APNICValid
116.50.74.0/23APNICValid
116.50.75.0/24APNICValid
116.50.76.0/22APNICValid
116.50.76.0/23APNICValid
116.50.77.0/24APNICValid
116.50.78.0/24APNICValid
116.50.79.0/24APNICValid
116.50.80.0/20APNICValid
116.50.80.0/21APNICValid
116.50.80.0/22APNICValid
116.50.80.0/23APNICValid
116.50.80.0/24APNIC, RADBValid
116.50.82.0/23APNICValid
116.50.82.0/24APNICValid
116.50.84.0/22APNICValid
116.50.84.0/23APNICValid
116.50.86.0/23APNICValid
116.50.86.0/24APNICValid
116.50.87.0/24APNICValid
116.50.88.0/21APNICValid
116.50.88.0/22APNICValid
116.50.88.0/23APNICValid
116.50.89.0/24APNICValid
116.50.90.0/23APNICValid
116.50.90.0/24APNICValid
116.50.92.0/22APNICValid
116.50.92.0/23APNICValid
116.50.92.0/24APNICValid
116.50.93.0/24APNICValid
116.50.94.0/23APNICValid
116.50.95.0/24APNICValid
116.50.96.0/19APNICValid
116.50.96.0/20APNICValid
116.50.96.0/21APNICValid
116.50.96.0/22APNICValid
116.50.96.0/24APNICValid
116.50.97.0/24APNICValid
116.50.98.0/23APNICValid
116.50.98.0/24APNICValid
116.50.100.0/22APNICValid
116.50.100.0/23APNICValid
116.50.100.0/24APNICValid
116.50.101.0/24APNICValid
116.50.102.0/23APNICValid
116.50.102.0/24APNICValid
116.50.103.0/24APNICValid
116.50.104.0/21APNICValid
116.50.104.0/22APNICValid
116.50.104.0/23APNICValid
116.50.104.0/24APNICValid
116.50.105.0/24APNICValid
116.50.106.0/23APNICValid
116.50.106.0/24APNICValid
116.50.107.0/24APNICValid
116.50.108.0/22APNICValid
116.50.108.0/23APNICValid
116.50.108.0/24APNICValid
116.50.109.0/24APNICValid
116.50.110.0/23APNICValid
116.50.110.0/24APNICValid
116.50.111.0/24APNICValid
116.50.112.0/20APNICValid
116.50.112.0/21APNICValid
116.50.112.0/22APNICValid
116.50.112.0/23APNICValid
116.50.112.0/24APNICValid
116.50.114.0/23APNICValid
116.50.114.0/24APNICValid
116.50.115.0/24APNICValid
116.50.116.0/22APNICValid
116.50.116.0/23APNICValid
116.50.116.0/24APNICValid
116.50.117.0/24APNICValid
116.50.118.0/23APNICValid
116.50.118.0/24APNICValid
116.50.119.0/24APNICValid
116.50.120.0/21APNICValid
116.50.120.0/22APNICValid
116.50.120.0/23APNICValid
116.50.120.0/24APNICValid
116.50.122.0/23APNICValid
116.50.122.0/24APNICValid
116.50.123.0/24APNICValid
116.50.124.0/22APNICValid
116.50.124.0/23APNICValid
116.50.124.0/24APNICValid
116.50.125.0/24APNICValid
116.50.126.0/23APNICValid
116.50.126.0/24APNICValid
116.50.127.0/24APNICValid
203.199.41.0/24APNICValid
2402:8e00::/33APNICNo ROA
2402:8e00::/35APNICNo ROA
2402:8e00:8000::/33APNICNo ROA

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.