HZ-P

BGP inherited
Cluster stats
Netblocks7
Cluster ID209652669
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 10 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
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.130.4.16/28 HZ-P APNIC ASSIGNED NON-PORTABLE ● high
61.164.57.0/29 HZ-P APNIC ASSIGNED NON-PORTABLE ● high
115.236.190.56/29 HZ-P APNIC ASSIGNED NON-PORTABLE ● high
122.224.90.200/29 HZ-P APNIC ASSIGNED NON-PORTABLE ● high
122.224.221.56/29 HZ-P APNIC ASSIGNED NON-PORTABLE ● high
183.129.210.96/29 HZ-P APNIC ASSIGNED NON-PORTABLE ● high
218.75.69.24/29 HZ-P APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
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.
  • Yhz Pri Sch via No.31,Jin-rong Street sub-allocation
  • Plzen Cz via T-Mobile Czech Republic a.s. sub-allocation
  • Planning via CNCGROUP IP network of ShangHai IDC sub-allocation
  • Hz Pl Sy via CNCGROUP IP network of ShangHai IDC sub-allocation
  • Hz Pl via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

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

NIC Handles

AC1602-AP CH122-AP HH2341-AP JY3458-AP LF1029-AP LQ1014-AP MAINT-CN-CHINANET-ZJ-HZ WB639-AP YX2398-AP ZQ1137-AP