DAPENG

BGP inherited
Cluster stats
Netblocks6
All fragments 14 blocks across 8 clusters
Cluster ID211801345
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 15 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
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.236.224.152/30 DAPENG APNIC ASSIGNED NON-PORTABLE ● high
180.168.12.72/30 DAPENG APNIC ASSIGNED NON-PORTABLE ● high
180.168.29.4/30 DAPENG APNIC ASSIGNED NON-PORTABLE ● high
180.168.31.160/30 DAPENG APNIC ASSIGNED NON-PORTABLE ● high
211.154.61.64/26 DAPENG APNIC ASSIGNED NON-PORTABLE ● low
221.11.7.180/30 dapeng_net APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “DAPENG” — 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.
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: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
No discrepancies found among checked blocks.

NIC Handles

CH153-AP CH679-AP CH679-AP FX324-AP FX324-AP LW153-AP MAINT-CHINANET-SH MAINT-CN-CNNIC-UNIHUB MAINT-CNCGROUP-SN YWZ6-AP YWZ6-AP ZB122-AP +3 more