bgpreport

Network · data from 2026-11-12

AS17436 ICICIBANK-AS - ICICIBANK Ltd, Banking, Mumbai

Registry name: ICICIBANK-AS - ICICIBANK Ltd, Banking, Mumbai, IN · not in PeeringDB

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

Announced routes

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

203.171.210.0/24 No ROA Other IRR onlyRADB 673 100% 66
203.171.211.0/24 No ROA Other IRR onlyRADB 673 100% 67
103.60.4.0/24 No ROA RIR databaseAPNIC 673 100% 66
103.87.40.0/23 No ROA RIR databaseAPNIC 673 100% 67
103.87.42.0/23 No ROA RIR databaseAPNIC 673 100% 66
203.27.235.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
203.189.92.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 67
103.60.5.0/24 No ROA RIR databaseAPNIC 671 100% 66
2001:df0:2fd::/48 No ROA RIR databaseAPNIC 636 100% 70
2001:df7:f400::/48 No ROA RIR databaseAPNIC 636 100% 70
2001:df7:f401::/48 No ROA RIR databaseAPNIC 636 100% 70
2001:df7:f402::/48 No ROA RIR databaseAPNIC 636 100% 70
2001:df7:f403::/48 No ROA RIR databaseAPNIC 636 100% 70
103.166.216.0/23 Valid RIR databaseAPNIC 673 100% 66
103.168.48.0/24 Valid RIR databaseAPNIC 673 100% 66
103.168.49.0/24 Valid RIR databaseAPNIC 673 100% 66
103.169.234.0/24 Valid RIR databaseAPNIC 673 100% 66
103.167.202.0/24 Valid RIR databaseAPNIC 672 100% 67
103.83.12.0/24 Valid RIR databaseAPNIC 671 100% 67
103.83.13.0/24 Valid RIR databaseAPNIC 671 100% 66
103.147.155.0/24 Valid RIR databaseAPNIC 671 100% 67
103.167.203.0/24 Valid RIR databaseAPNIC 671 100% 66
103.169.235.0/24 Valid RIR databaseAPNIC 671 100% 67
103.217.73.0/24 Valid RIR databaseAPNIC 671 100% 66

AS-SET

AS17436 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 27 are in fix.csv.

  • ROA: none13
  • Route object: RIR2
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none203.171.210.0/24No ROA covers it. Add a ROA for AS17436, maxLength 24.673 of 673
Route object: RIR203.171.210.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.171.211.0/24No ROA covers it. Add a ROA for AS17436, maxLength 24.673 of 673
Route object: RIR203.171.211.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.60.4.0/24No ROA covers it. Add a ROA for AS17436, maxLength 24.673 of 673
ROA: none103.87.40.0/23No ROA covers it. Add a ROA for AS17436, maxLength 23.673 of 673
ROA: none103.87.42.0/23No ROA covers it. Add a ROA for AS17436, maxLength 23.673 of 673
ROA: none203.27.235.0/24No ROA covers it. Add a ROA for AS17436, maxLength 24.673 of 673
ROA: none203.189.92.0/24No ROA covers it. Add a ROA for AS17436, maxLength 24.673 of 673
ROA: none103.60.5.0/24No ROA covers it. Add a ROA for AS17436, maxLength 24.671 of 673
ROA: none2001:df0:2fd::/48No ROA covers it. Add a ROA for AS17436, maxLength 48.636 of 636
ROA: none2001:df7:f400::/48No ROA covers it. Add a ROA for AS17436, maxLength 48.636 of 636
ROA: none2001:df7:f401::/48No ROA covers it. Add a ROA for AS17436, maxLength 48.636 of 636
ROA: none2001:df7:f402::/48No ROA covers it. Add a ROA for AS17436, maxLength 48.636 of 636
ROA: none2001:df7:f403::/48No ROA covers it. Add a ROA for AS17436, maxLength 48.636 of 636

Route objects not announced

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

103.60.4.0/23APNICNo ROA
103.83.12.0/23APNICValid
103.166.216.0/24APNICValid
103.166.217.0/24APNICValid
103.167.202.0/23APNICValid
103.168.48.0/23APNICValid
103.169.234.0/23APNICValid
103.181.236.0/23APNICValid
103.181.236.0/24APNICValid
103.181.237.0/24APNICValid
203.171.210.0/23APNIC, RADBNo ROA
2001:df0:2fd:2000::/52APNICNo 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.