bgpreport

Network · data from 2026-11-12

AS132384 DCIPL-AS-AP - Deloitte Consulting India Pvt. Ltd

Registry name: DCIPL-AS-AP - Deloitte Consulting India Pvt. Ltd, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132384, 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.
103.76.232.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
103.76.232.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
103.76.232.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.76.233.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.76.234.0/24 Valid RIR databaseAPNIC 673 100% 67
103.76.235.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
116.206.144.0/23 Valid RIR databaseAPNIC 673 100% 66
116.206.144.0/24 Valid RIR databaseAPNIC 673 100% 66
116.206.145.0/24 Valid RIR databaseAPNIC 673 100% 67
167.219.50.0/23 Valid RIR databaseAPNIC 673 100% 66
167.219.52.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.52.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.53.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
167.219.56.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.56.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.57.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
167.219.58.0/23 Valid RIR databaseAPNIC 673 100% 66
167.219.58.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.59.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
167.219.60.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.60.0/24 Valid RIR databaseAPNIC 673 100% 66
167.219.61.0/24 Valid RIR databaseAPNIC 673 100% 67
167.219.62.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.62.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
167.219.63.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
167.219.132.0/23 Valid RIR databaseAPNIC 673 100% 66
167.219.132.0/24 Valid RIR databaseAPNIC 673 100% 66
167.219.133.0/24 Valid RIR databaseAPNIC 673 100% 67
167.219.54.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
2407:7a80::/42 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
2407:7a80:10::/45 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
2407:7a80:10::/46 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
2407:7a80:15::/48 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2

AS-SET

AS132384 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 24 are in fix.csv.

  • Route object: not announced24

Route objects not announced

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

103.76.234.0/23APNIC, RADBValid
116.206.146.0/23APNICValid
116.206.146.0/24APNICValid
116.206.147.0/24APNICValid
167.219.48.0/23APNIC, RADBValid
167.219.48.0/24APNICValid
167.219.49.0/24APNICValid
167.219.50.0/24APNIC, RADBValid
167.219.51.0/24APNIC, RADBValid
167.219.54.0/23APNICValid
167.219.55.0/24APNIC, RADBValid
2407:7a80:10::/47APNIC, RADBValid
2407:7a80:12::/48APNIC, RADBValid
2407:7a80:13::/48APNIC, RADBValid
2407:7a80:14::/48APNIC, RADBValid
2407:7a80:20::/44APNICValid
2407:7a80:20::/45APNIC, RADBValid
2407:7a80:20::/48APNIC, RADBValid
2407:7a80:21::/48APNIC, RADBValid
2407:7a80:22::/48APNIC, RADBValid
2407:7a80:23::/48APNIC, RADBValid
2407:7a80:24::/46APNIC, RADBValid
2407:7a80:28::/48APNICValid
2407:7a80:29::/48APNICValid

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.