FENGSHEN

BGP inherited
Cluster stats
Netblocks7
All fragments 8 blocks across 2 clusters
Cluster ID208803684
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 16 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
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.236.104.208/29 FENGSHEN APNIC ASSIGNED NON-PORTABLE ● high
116.236.104.216/29 FENGSHEN APNIC ASSIGNED NON-PORTABLE ● high
116.236.104.240/29 FENGSHEN APNIC ASSIGNED NON-PORTABLE ● high
116.236.104.248/29 FENGSHEN APNIC ASSIGNED NON-PORTABLE ● high
116.236.105.16/29 FENGSHEN APNIC ASSIGNED NON-PORTABLE ● high
116.236.105.24/29 FENGSHEN APNIC ASSIGNED NON-PORTABLE ● high
218.1.104.92/30 FENGSHEN-CO APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “FENGSHEN” — 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: 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

AC1591-AP GZ1060-AP GZ1060-AP GZ1061-AP GZ1061-AP GZ1062-AP GZ1062-AP GZ1063-AP GZ1063-AP GZ1064-AP GZ1064-AP GZ1065-AP +4 more