bgpreport

Network · data from 2026-11-12

AS17648 HECL-AS - Hughes Communications India Private Limited

Registry name: HECL-AS - Hughes Communications India Private Limited, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS17648, 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.
110.50.55.0/24 Invalid: maxLength Nonecovered by 110.50.32.0/19 150 22% 53
110.50.35.0/24 Invalid: maxLength RIR databaseAPNIC 135 20% 53
110.50.36.0/24 Invalid: maxLength RIR databaseAPNIC 135 20% 53
110.50.37.0/24 Invalid: maxLength RIR databaseAPNIC 135 20% 53
110.50.32.0/19 No ROA RIR databaseAPNIC, RADB 673 100% 66
2406:2e00::/32 Valid None 636 100% 70
110.50.60.0/24 Valid RIR databaseAPNIC 673 100% 66
110.50.61.0/24 Valid RIR databaseAPNIC 673 100% 66
110.50.62.0/24 Valid RIR databaseAPNIC 673 100% 66
202.134.192.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.193.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.194.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.195.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.196.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.197.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.198.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.199.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.200.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.201.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.202.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.203.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.204.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.205.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
202.134.206.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.134.207.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66

AS-SET

AS17648 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 10 are in fix.csv.

  • ROA: maxLength4
  • ROA: none1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength110.50.55.0/24ROA 110.50.48.0/21 AS17648 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 110.50.55.0/24.150 of 673
Route object: none110.50.55.0/24No route object for it. A route object for 110.50.32.0/19 with origin AS17648 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17648 in the RIR database for the space.150 of 673
ROA: maxLength110.50.35.0/24ROA 110.50.32.0/20 AS17648 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 110.50.35.0/24.135 of 673
ROA: maxLength110.50.36.0/24ROA 110.50.32.0/20 AS17648 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 110.50.36.0/24.135 of 673
ROA: maxLength110.50.37.0/24ROA 110.50.32.0/20 AS17648 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 110.50.37.0/24.135 of 673
ROA: none110.50.32.0/19No ROA covers it. Add a ROA for AS17648, maxLength 19.673 of 673
Route object: none2406:2e00::/32No route object for it. Add a route object with origin AS17648 in the RIR database for the space.636 of 636

Route objects not announced

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

110.50.32.0/20APNICValid
110.50.63.0/24APNICValid
202.134.192.0/20APNIC, RADBValid

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.