HGC
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 66 · 1,932 IPv4 addresses |
| IPv6 | 27 prefixes (largest 2001:41f0:14ea::/48) |
| Registered in | Hong Kong (14) · Thailand (5) · United States (4) · Germany (2) · Japan (2) · France (2) |
| All fragments | 2,279 blocks across 13 clusters |
| Cluster ID | 213300065 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 18 shared RIR contact/maintainer handles |
| Registry names | 6 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
Footprint over time
6 weekly snapshots · JSON
66
+2 netblocks since 2026-07-05
2026-07-05
peak 66
2026-07-26
IP Ranges (66)
showing 50 of 66 — see all — ⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 27.111.228.59/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 36.255.56.16/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 37.49.232.105/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 37.49.236.221/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 45.114.21.204/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 80.81.194.166/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 80.249.210.31/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 101.203.89.188/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 103.16.102.184/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 103.100.140.47/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 103.203.158.175/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 103.247.139.28/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 103.247.139.39/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 112.137.24.99/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 112.137.26.6/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 123.255.90.35/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 123.255.90.140/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 123.255.91.41/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 123.255.91.101/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 123.255.92.33/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 139.150.100.211/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 185.1.47.84/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 195.66.224.100/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 198.32.243.96/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 206.72.210.114/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 206.72.211.57/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 206.82.105.36/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 218.100.44.176/32 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:6::9304:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:13::210:114/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:13::211:57/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:504:36::2458:0:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::2458:0:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a500:9304:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:4::2458:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:36::2458:0:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54::221/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:54:5::105/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a023/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a08c/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a129/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a165/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:7fa:0:1::ca28:a221/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:4::9304:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:7::9304:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:c::9304:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:10::77/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:de8:12:100::184/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:296::a500:9304:1/128 | HGC | PEERINGDB | ASSIGNED | ● high |
| 2001:df0:296::a500:9304:2/128 | HGC | PEERINGDB | ASSIGNED | ● high |
IPv6 ranges (27)
showing the 15 largest allocationsNetwork trust
what's this?
RPKI hygiene: B
how networks compare →
89.4%
of checked blocks have valid RPKI ROA coverage
(59 of 66)
Possible discrepancies (1)
These blocks are registered to HGC but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 119.13.30.0/24 /24 | authorized for AS38794 — Renaissance Phuket Resort & Spa |
NIC Handles
AH1052-AP
AH921-AP
AS9304
AU80-AP
BDSH1-AP
BDSH1-AP
DUMY-RIPE
DUMY-RIPE
GO-JOR
IH17-AP
IH17-AP
MAINT-HK-HGCADMIN
+6 more