bgpreport

Network · data from 2026-11-12

AS139820 HG TELECOMMUNICATION PRIVATE LIMITED

Registry name: HG1-AS-AP - HG TELECOMMUNICATION PRIVATE LIMITED, PK · PeeringDB

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

Announced routes

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

160.22.141.0/24 No ROA None 673 100% 67
39.62.1.0/24 Valid RIR databaseAPNIC 673 100% 68
39.62.2.0/24 Valid RIR databaseAPNIC 673 100% 68
59.103.32.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.33.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.34.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.35.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.36.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.37.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.40.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.41.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.43.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.47.0/24 Valid RIR databaseAPNIC 673 100% 66
103.12.40.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.12.42.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.12.43.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.62.235.0/24 Valid RIR databaseAPNIC 673 100% 68
103.148.92.0/24 Valid RIR databaseAPNIC 673 100% 68
103.155.18.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.155.19.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
144.79.56.0/24 Valid RIR databaseAPNIC 673 100% 66
160.30.174.0/24 Valid RIR databaseAPNIC 673 100% 66
59.103.38.0/24 Valid RIR databaseAPNIC 672 100% 66
59.103.39.0/24 Valid RIR databaseAPNIC 672 100% 66
59.103.44.0/24 Valid RIR databaseAPNIC 672 100% 66
59.103.46.0/24 Valid RIR databaseAPNIC 672 100% 66
103.86.88.0/24 Valid RIR databaseAPNIC 672 100% 67
103.86.89.0/24 Valid RIR databaseAPNIC 672 100% 66
103.180.242.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

AS139820's PeeringDB record names no 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 115 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced113
ChangePrefix or setDetailFull-table peers
ROA: none160.22.141.0/24No ROA covers it. Add a ROA for AS139820, maxLength 24.673 of 673
Route object: none160.22.141.0/24No route object for it. Add a route object with origin AS139820 in the RIR database for the space.673 of 673

Route objects not announced

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

39.62.0.0/19APNICValid
39.62.0.0/20APNICValid
39.62.0.0/21APNICValid
39.62.0.0/22APNICValid
39.62.0.0/23APNICValid
39.62.0.0/24APNICValid
39.62.2.0/23APNICValid
39.62.3.0/24APNICValid
39.62.4.0/22APNICValid
39.62.4.0/23APNICValid
39.62.4.0/24APNICValid
39.62.5.0/24APNICValid
39.62.6.0/23APNICValid
39.62.6.0/24APNICValid
39.62.7.0/24APNICValid
39.62.8.0/21APNICValid
39.62.8.0/22APNICValid
39.62.8.0/23APNICValid
39.62.8.0/24APNICValid
39.62.9.0/24APNICValid
39.62.10.0/23APNICValid
39.62.10.0/24APNICValid
39.62.11.0/24APNICValid
39.62.12.0/22APNICValid
39.62.12.0/23APNICValid
39.62.12.0/24APNICValid
39.62.13.0/24APNICValid
39.62.14.0/23APNICValid
39.62.14.0/24APNICValid
39.62.15.0/24APNICValid
39.62.16.0/20APNICValid
39.62.16.0/21APNICValid
39.62.16.0/22APNICValid
39.62.16.0/23APNICValid
39.62.16.0/24APNICValid
39.62.17.0/24APNICValid
39.62.18.0/23APNICValid
39.62.18.0/24APNICValid
39.62.19.0/24APNICValid
39.62.20.0/22APNICValid
39.62.20.0/23APNICValid
39.62.20.0/24APNICValid
39.62.21.0/24APNICValid
39.62.22.0/23APNICValid
39.62.22.0/24APNICValid
39.62.23.0/24APNICValid
39.62.24.0/21APNICValid
39.62.24.0/22APNICValid
39.62.24.0/23APNICValid
39.62.24.0/24APNICValid
39.62.25.0/24APNICValid
39.62.26.0/23APNICValid
39.62.26.0/24APNICValid
39.62.27.0/24APNICValid
39.62.28.0/22APNICValid
39.62.28.0/23APNICValid
39.62.28.0/24APNICValid
39.62.29.0/24APNICValid
39.62.30.0/23APNICValid
39.62.30.0/24APNICValid
39.62.31.0/24APNICValid
59.103.32.0/19APNICValid
59.103.32.0/20APNICValid
59.103.32.0/21APNICValid
59.103.32.0/22APNICValid
59.103.32.0/23APNICValid
59.103.34.0/23APNICValid
59.103.36.0/22APNICValid
59.103.36.0/23APNICValid
59.103.38.0/23APNICValid
59.103.40.0/21APNICValid
59.103.40.0/22APNICValid
59.103.40.0/23APNICValid
59.103.42.0/23APNICValid
59.103.42.0/24APNICValid
59.103.44.0/22APNICValid
59.103.44.0/23APNICValid
59.103.45.0/24APNICValid
59.103.46.0/23APNICValid
59.103.48.0/20APNICValid
59.103.48.0/21APNICValid
59.103.48.0/22APNICValid
59.103.48.0/23APNICValid
59.103.48.0/24APNICValid
59.103.49.0/24APNICValid
59.103.50.0/23APNICValid
59.103.50.0/24APNICValid
59.103.51.0/24APNICValid
59.103.52.0/22APNICValid
59.103.52.0/23APNICValid
59.103.52.0/24APNICValid
59.103.53.0/24APNICValid
59.103.54.0/23APNICValid
59.103.54.0/24APNICValid
59.103.55.0/24APNICValid
59.103.56.0/21APNICValid
59.103.56.0/22APNICValid
59.103.56.0/23APNICValid
59.103.56.0/24APNICValid
59.103.57.0/24APNICValid
59.103.58.0/23APNICValid
59.103.58.0/24APNICValid
59.103.59.0/24APNICValid
59.103.60.0/22APNICValid
59.103.60.0/23APNICValid
59.103.60.0/24APNICValid
59.103.61.0/24APNICValid
59.103.62.0/23APNICValid
59.103.62.0/24APNICValid
59.103.63.0/24APNICValid
103.158.236.0/24APNICValid
202.155.150.0/24RADBValid
2401:be60::/32APNICValid

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.