ZHUFU

BGP inherited
Cluster stats
Netblocks7
Cluster ID209013129
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 15 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
116.228.138.132/30 ZHUFU APNIC ASSIGNED NON-PORTABLE ● high
116.228.138.184/30 ZHUFU APNIC ASSIGNED NON-PORTABLE ● high
116.228.184.108/30 ZHUFU APNIC ASSIGNED NON-PORTABLE ● high
116.236.224.96/29 ZHUFU APNIC ASSIGNED NON-PORTABLE ● high
116.236.235.32/30 ZHUFU APNIC ASSIGNED NON-PORTABLE ● high
116.236.246.160/29 ZHUFU APNIC ASSIGNED NON-PORTABLE ● high
218.1.111.76/30 ZHUFU 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.

Network trust

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

NIC Handles

JRS2-AP JRS2-AP JRS3-AP JRS3-AP JRS4-AP JRS4-AP JRS5-AP JRS5-AP JRS6-AP JRS6-AP LLL34-AP LLL34-AP +3 more