HETING

BGP inherited

Cluster stats

Netblocks	6
All fragments	7 blocks across 2 clusters
Cluster ID	210117444
Registry	APNIC
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 13 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
116.228.139.176/30	HETING	APNIC	ASSIGNED NON-PORTABLE	● high
116.236.190.248/30	HETING	APNIC	ASSIGNED NON-PORTABLE	● high
116.236.235.252/30	HETING	APNIC	ASSIGNED NON-PORTABLE	● high
180.168.30.240/30	HETING	APNIC	ASSIGNED NON-PORTABLE	● high
180.168.31.4/30	HETING	APNIC	ASSIGNED NON-PORTABLE	● high
180.168.47.12/30	HETING	APNIC	ASSIGNED NON-PORTABLE	● high

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “HETING” — 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.

HETING-JIULOU 1 blocks

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

jiangheting sub-allocation
Jiansheting Gov via CNCGROUP IP network of ShangHai IDC sub-allocation
shengjiansheting via CNCGROUP IP network of ShangHai IDC sub-allocation
yangheting sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)

No discrepancies found among checked blocks.

NIC Handles

HJL32-AP HJL32-AP HJL33-AP HJL33-AP LJ2012-AP LJ2012-AP LJ669-AP LJ669-AP MAINT-CHINANET-SH MM949-AP MM949-AP WQ506-AP +1 more