LZZH

BGP inherited
Cluster stats
Netblocks9
Cluster ID210213960
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 20 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
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
116.236.171.24/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
180.168.169.200/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
222.66.160.80/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
222.66.160.120/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
222.66.160.152/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
222.66.160.176/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
222.66.160.192/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
222.66.160.200/29 LZZH APNIC ASSIGNED NON-PORTABLE ● high
222.66.160.208/29 LZZH 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.
  • lylzzhf via CNCGROUP IP network of ShangHai IDC sub-allocation

Network trust

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

NIC Handles

AC1591-AP MAINT-CHINANET-SH YSB10-AP YSB10-AP YSB11-AP YSB11-AP YSB12-AP YSB12-AP YSB13-AP YSB13-AP YSB14-AP YSB14-AP +8 more