HTCN

BGP inherited
Cluster stats
Netblocks9 · 1,023 IPv4 addresses
All fragments 10 blocks across 2 clusters
Cluster ID212095978
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.246.232.133/32 HTCN PEERINGDB ASSIGNED ● high
203.190.230.16/32 HTCN PEERINGDB ASSIGNED ● high
210.171.224.133/32 HTCN PEERINGDB ASSIGNED ● high
218.100.9.85/32 HTCN PEERINGDB ASSIGNED ● high
2001:de8:5::7668:1/128 HTCN PEERINGDB ASSIGNED ● high
2001:de8:8::7668:1/128 HTCN PEERINGDB ASSIGNED ● high
2001:de8:8:6::7668:1/128 HTCN PEERINGDB ASSIGNED ● high
2001:de8:c:2::7668:1/128 HTCN PEERINGDB ASSIGNED ● high
103.210.84.0/22 HTCN APNIC ALLOCATED PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “HTCN” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (6 of 9)
No discrepancies found among checked blocks.

NIC Handles

AS7668 JNIC1-AP JNIC1-AP MAINT-JPNIC