bgpreport

Network · data from 2026-11-12

AS17466 GENPACT-AS-AP - Genpact India Private Limited

Registry name: GENPACT-AS-AP - Genpact India Private Limited, IN · not in PeeringDB

27IPv4 routes 66.7% RPKI valid · 85.2% with a route object
0IPv6 routes
2RPKI invalid 1 origin · 1 maxLength
7No ROA 4 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
44Route objects not announced registered with origin AS17466, seen from no peer

Announced routes

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

216.68.238.0/24 Invalid: origin None 28 4%low visibility 19
58.2.1.0/24 Invalid: maxLength Nonecovered by 58.2.0.0/20 6 1%low visibility 3
124.4.248.0/24 No ROA None 673 100% 67
124.4.249.0/24 No ROA None 673 100% 67
8.19.113.0/24 No ROA Other IRR onlyRADB 673 100% 67
124.4.200.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 68
124.4.250.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
124.4.251.0/24 No ROA Other IRR onlyNTTCOM, RADB 671 100% 69
182.94.236.0/22 No ROA RIR databaseAPNIC 673 100% 67
58.2.128.0/19 Valid RIR databaseAPNIC 673 100% 67
124.4.44.0/24 Valid RIR databaseAPNIC 673 100% 69
124.4.120.0/23 Valid RIR databaseAPNIC 673 100% 66
124.4.120.0/24 Valid RIR databaseAPNIC 673 100% 67
124.4.121.0/24 Valid RIR databaseAPNIC 673 100% 66
124.4.122.0/23 Valid RIR databaseAPNIC 673 100% 67
124.4.122.0/24 Valid RIR databaseAPNIC 673 100% 67
124.4.123.0/24 Valid RIR databaseAPNIC 673 100% 67
182.94.236.0/23 Valid RIR databaseAPNIC 673 100% 66
182.94.236.0/24 Valid RIR databaseAPNIC 673 100% 67
182.94.237.0/24 Valid RIR databaseAPNIC 673 100% 67
182.94.238.0/23 Valid RIR databaseAPNIC 673 100% 67
182.94.238.0/24 Valid RIR databaseAPNIC 673 100% 67
182.94.239.0/24 Valid RIR databaseAPNIC 673 100% 67
182.94.240.0/24 Valid RIR databaseAPNIC 673 100% 67
58.2.16.0/20 Valid RIR databaseAPNIC 667 99% 67
58.2.16.0/22 Valid RIR databaseAPNIC 667 99% 67
58.2.20.0/22 Valid RIR databaseAPNIC 667 99% 67

AS-SET

AS17466 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 61 are in fix.csv.

  • ROA: origin1
  • ROA: maxLength1
  • ROA: none7
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced44
ChangePrefix or setDetailFull-table peers
ROA: origin216.68.238.0/24ROAs covering it name AS6181, not AS17466. If AS17466 should announce it, add a ROA for AS17466.28 of 673
Route object: none216.68.238.0/24No route object for it. Add a route object with origin AS17466 in the RIR database for the space.28 of 673
ROA: maxLength58.2.1.0/24ROA 58.2.0.0/20 AS17466 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 58.2.1.0/24.6 of 673
Route object: none58.2.1.0/24No route object for it. A route object for 58.2.0.0/20 with origin AS17466 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17466 in the RIR database for the space.6 of 673
ROA: none124.4.248.0/24No ROA covers it. Add a ROA for AS17466, maxLength 24.673 of 673
Route object: none124.4.248.0/24No route object for it. Add a route object with origin AS17466 in the RIR database for the space.673 of 673
ROA: none124.4.249.0/24No ROA covers it. Add a ROA for AS17466, maxLength 24.673 of 673
Route object: none124.4.249.0/24No route object for it. Add a route object with origin AS17466 in the RIR database for the space.673 of 673
ROA: none8.19.113.0/24No ROA covers it. Add a ROA for AS17466, maxLength 24.673 of 673
Route object: RIR8.19.113.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none124.4.200.0/22No ROA covers it. Add a ROA for AS17466, maxLength 22.671 of 673
Route object: RIR124.4.200.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none124.4.250.0/24No ROA covers it. Add a ROA for AS17466, maxLength 24.671 of 673
Route object: RIR124.4.250.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none124.4.251.0/24No ROA covers it. Add a ROA for AS17466, maxLength 24.671 of 673
Route object: RIR124.4.251.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none182.94.236.0/22No ROA covers it. Add a ROA for AS17466, maxLength 22.673 of 673

Route objects not announced

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

58.2.0.0/20APNICValid
58.2.16.0/21APNICValid
58.2.32.0/19APNICValid
58.2.192.0/19APNICValid
58.2.224.0/21APNICValid
58.2.232.0/22APNICValid
58.2.236.0/22APNIC, RADBNo ROA
58.2.236.0/23RADBNo ROA
58.2.236.0/24APNICNo ROA
58.2.237.0/24APNIC, RADBNo ROA
58.2.238.0/24APNIC, RADBNo ROA
58.2.239.0/24APNIC, RADBNo ROA
58.2.240.0/20APNICValid
119.43.0.0/17APNICValid
119.43.128.0/18APNICValid
119.43.192.0/21APNICValid
119.43.200.0/22RADBNo ROA
119.43.205.0/24APNICValid
119.43.206.0/23APNICValid
119.43.208.0/20APNICValid
119.43.224.0/19APNICValid
124.4.0.0/19APNICValid
124.4.32.0/21APNICValid
124.4.40.0/22APNICValid
124.4.45.0/24APNICValid
124.4.46.0/23APNICValid
124.4.48.0/20APNICValid
124.4.64.0/18APNICValid
124.4.128.0/18APNICValid
124.4.192.0/21APNICValid
124.4.204.0/22APNICValid
124.4.208.0/20APNICValid
124.4.252.0/22APNICValid
182.94.0.0/17APNICValid
182.94.128.0/18APNICValid
182.94.192.0/19APNICValid
182.94.224.0/21APNICValid
182.94.232.0/22APNICValid
182.94.240.0/22APNICNo ROA
182.94.241.0/24APNICValid
182.94.242.0/23APNICValid
182.94.244.0/22APNICValid
182.94.248.0/21APNICValid
216.195.77.0/24ALTDB, RADBNo 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.