bgpreport

Network · data from 2026-11-12

AS17817 DAKSH-IN - Concentrix Daksh Services India Private Limited

Registry name: DAKSH-IN - Concentrix Daksh Services India Private Limited, ID · not in PeeringDB

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

Announced routes

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

116.90.246.0/23 No ROA None 673 100% 66
116.90.254.0/24 No ROA Nonecovered by 116.90.254.0/23 672 100% 66
116.90.240.0/24 No ROA Other IRR onlyRADB 673 100% 70
203.92.192.0/24 No ROA Other IRR onlyRADB 673 100% 70
203.92.197.0/24 No ROA Other IRR onlyRADB 673 100% 70
116.90.250.0/24 No ROA Other IRR onlyRADB 672 100% 67
203.92.194.0/24 No ROA Other IRR onlyRADB 672 100% 67
116.90.252.0/24 No ROA Other IRR onlyRADB 671 100% 66
203.92.193.0/24 No ROA Other IRR onlyRADB 671 100% 66
203.92.194.0/23 No ROA Other IRR onlyRADB 671 100% 66
203.92.195.0/24 No ROA Other IRR onlyRADB 671 100% 66
116.90.254.0/23 No ROA Other IRR onlyRADB 670 100% 67
116.90.246.0/24 No ROA Other IRR onlyRADB 558 83% 66
116.90.248.0/24 No ROA RIR databaseAPNIC 673 100% 70
116.90.255.0/24 No ROA RIR databaseAPNIC 673 100% 70
203.92.196.0/24 No ROA RIR databaseAPNIC 673 100% 70
203.92.198.0/24 No ROA RIR databaseAPNIC 672 100% 67
116.90.245.0/24 No ROA RIR databaseAPNIC, RADB 671 100% 67
203.92.198.0/23 No ROA RIR databaseAPNIC 671 100% 66
221.120.106.0/24 No ROA RIR databaseAPNIC 671 100% 66
221.120.104.0/24 No ROA RIR databaseAPNIC 670 100% 67
221.120.110.0/24 No ROA RIR databaseAPNIC 670 100% 67
221.120.111.0/24 No ROA RIR databaseAPNIC 668 99% 67

AS-SET

AS17817 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 57 are in fix.csv.

  • ROA: none23
  • Route object: none2
  • Route object: RIR11
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none116.90.246.0/23No ROA covers it. Add a ROA for AS17817, maxLength 23.673 of 673
Route object: none116.90.246.0/23No route object for it. Add a route object with origin AS17817 in the RIR database for the space.673 of 673
ROA: none116.90.254.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.672 of 673
Route object: none116.90.254.0/24No route object for it. A route object for 116.90.254.0/23 with origin AS17817 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17817 in the RIR database for the space.672 of 673
ROA: none116.90.240.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.673 of 673
Route object: RIR116.90.240.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.92.192.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.673 of 673
Route object: RIR203.92.192.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none203.92.197.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.673 of 673
Route object: RIR203.92.197.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none116.90.250.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.672 of 673
Route object: RIR116.90.250.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.92.194.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.672 of 673
Route object: RIR203.92.194.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none116.90.252.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.671 of 673
Route object: RIR116.90.252.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.92.193.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.671 of 673
Route object: RIR203.92.193.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.92.194.0/23No ROA covers it. Add a ROA for AS17817, maxLength 23.671 of 673
Route object: RIR203.92.194.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none203.92.195.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.671 of 673
Route object: RIR203.92.195.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none116.90.254.0/23No ROA covers it. Add a ROA for AS17817, maxLength 23.670 of 673
Route object: RIR116.90.254.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none116.90.246.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.558 of 673
Route object: RIR116.90.246.0/24Route object only in RADB. Add it in the RIR database for the space.558 of 673
ROA: none116.90.248.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.673 of 673
ROA: none116.90.255.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.673 of 673
ROA: none203.92.196.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.673 of 673
ROA: none203.92.198.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.672 of 673
ROA: none116.90.245.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.671 of 673
ROA: none203.92.198.0/23No ROA covers it. Add a ROA for AS17817, maxLength 23.671 of 673
ROA: none221.120.106.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.671 of 673
ROA: none221.120.104.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.670 of 673
ROA: none221.120.110.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.670 of 673
ROA: none221.120.111.0/24No ROA covers it. Add a ROA for AS17817, maxLength 24.668 of 673

Route objects not announced

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

116.90.247.0/24RADBNo ROA
116.90.251.0/24RADBNo ROA
116.90.252.0/23RADBNo ROA
116.90.253.0/24RADBNo ROA
203.92.192.0/22RADBNo ROA
203.92.192.0/23RADBNo ROA
203.92.196.0/23APNICNo ROA
203.92.206.0/23APNICNo ROA
203.92.206.0/24RADBNo ROA
203.92.207.0/24APNICNo ROA
221.120.104.0/21APNICNo ROA
221.120.104.0/22APNICNo ROA
221.120.104.0/23APNICNo ROA
221.120.105.0/24APNICNo ROA
221.120.106.0/23APNICNo ROA
221.120.107.0/24APNICNo ROA
221.120.108.0/22APNICNo ROA
221.120.108.0/23APNICNo ROA
221.120.108.0/24APNICNo ROA
221.120.109.0/24APNICNo ROA
221.120.110.0/23APNICNo 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.