bgpreport

Network · data from 2026-11-12

AS137996 HGC Global Communications

Registry name: HGCI-AS-AP - HGC Global Communications (Philippines), Inc., PH · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS137996, 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.170.129.0/24 No ROA RIR databaseAPNIC 672 100% 66
103.120.4.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.120.5.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.247.228.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.247.229.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
103.247.230.0/24 Valid RIR databaseAPNIC 673 100% 66
45.196.153.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 66
154.209.3.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 66
45.204.249.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 66
2407:b140:1379::/48 Valid RIR databaseAPNIC 636 100% 69

AS-SET

AS137996'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 3 are in fix.csv.

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none103.170.129.0/24No ROA covers it. Add a ROA for AS137996, maxLength 24.672 of 673

Route objects not announced

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

45.195.198.0/24AFRINICInvalid: origin
103.120.4.0/23NTTCOMNo 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.