bgpreport

Network · data from 2026-11-12

AS38174 CAPGEMINITECH-AS-AP - Capgemini Technology Services India Limited

Registry name: CAPGEMINITECH-AS-AP - Capgemini Technology Services India Limited, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38174, 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.
202.60.60.0/23 Valid RIR databaseAPNIC 673 100% 66
202.60.61.0/24 Valid RIR databaseAPNIC 673 100% 66
202.60.62.0/23 Valid RIR databaseAPNIC 673 100% 66
202.60.63.0/24 Valid RIR databaseAPNIC 673 100% 66
203.189.180.0/22 Valid RIR databaseAPNIC 673 100% 66
203.189.180.0/23 Valid RIR databaseAPNIC 673 100% 66
203.191.34.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
203.191.35.0/24 Valid RIR databaseAPNIC 673 100% 66
120.29.234.0/23 Valid RIR databaseAPNIC 672 100% 66
120.29.235.0/24 Valid RIR databaseAPNIC 672 100% 66
123.242.246.0/23 Valid RIR databaseAPNIC 672 100% 66
123.242.247.0/24 Valid RIR databaseAPNIC 672 100% 66
123.242.254.0/23 Valid RIR databaseAPNIC 672 100% 66
123.242.255.0/24 Valid RIR databaseAPNIC 672 100% 66
202.60.60.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.60.62.0/24 Valid RIR databaseAPNIC 672 100% 67
203.189.182.0/23 Valid RIR databaseAPNIC 672 100% 67
203.191.34.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
120.29.234.0/24 Valid RIR databaseAPNIC 671 100% 67
123.242.246.0/24 Valid RIR databaseAPNIC 671 100% 67
123.242.252.0/23 Valid RIR databaseAPNIC 671 100% 66
123.242.252.0/24 Valid RIR databaseAPNIC 671 100% 66
123.242.253.0/24 Valid RIR databaseAPNIC 671 100% 67
123.242.254.0/24 Valid RIR databaseAPNIC 671 100% 67

AS-SET

AS38174 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 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

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

120.29.239.0/24APNICValid
123.242.244.0/22APNICValid
123.242.244.0/23APNICValid
123.242.244.0/24APNICValid
123.242.245.0/24APNICValid
202.60.60.0/22APNICNo ROA
202.61.10.0/23APNICValid
202.61.10.0/24APNICValid
202.61.11.0/24APNICValid
203.189.180.0/24APNICValid
203.189.181.0/24APNICValid
203.189.182.0/24APNICValid
203.189.183.0/24APNICValid

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.