bgpreport

Network · data from 2026-11-12

AS137611 HCCI-AS-IN - Hexagon Capability Center India Pvt Ltd

Registry name: HCCI-AS-IN - Hexagon Capability Center India Pvt Ltd, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137611, 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.117.68.0/22 No ROA RIR databaseAPNIC 672 100% 66
2001:df5:a100::/48 No ROA RIR databaseAPNIC 636 100% 67
103.117.68.0/24 Valid RIR databaseAPNIC 673 100% 66
103.117.69.0/24 Valid RIR databaseAPNIC 673 100% 66
103.117.71.0/24 Valid RIR databaseAPNIC 673 100% 66
103.117.70.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

AS137611 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 9 are in fix.csv.

  • ROA: none2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none103.117.68.0/22No ROA covers it. Add a ROA for AS137611, maxLength 22.672 of 673
ROA: none2001:df5:a100::/48No ROA covers it. Add a ROA for AS137611, maxLength 48.636 of 636

Route objects not announced

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

103.117.68.0/23APNICNo ROA
103.117.70.0/23APNICNo ROA
2001:df5:a100::/64APNICNo ROA
2001:df5:a100:1::/64APNICNo ROA
2001:df5:a100:2::/64APNICNo ROA
2001:df5:a100:3::/64APNICNo ROA
2001:df5:a100:4::/64APNICNo 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.