fengcheng

Registry
Cluster stats
Netblocks8
All fragments 16 blocks across 9 clusters
Cluster ID208886156
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 14 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
116.236.225.172/30 FENGCHENG APNIC ASSIGNED NON-PORTABLE ● high
180.168.40.92/30 FENGCHENG APNIC ASSIGNED NON-PORTABLE ● high
180.168.175.80/30 FENGCHENG APNIC ASSIGNED NON-PORTABLE ● high
180.169.36.68/30 FENGCHENG APNIC ASSIGNED NON-PORTABLE ● high
58.254.204.146/32 fengcheng APNIC ASSIGNED NON-PORTABLE ● low
58.254.204.147/32 fengcheng APNIC ASSIGNED NON-PORTABLE ● low
221.4.149.194/32 fengcheng APNIC ASSIGNED NON-PORTABLE ● low
221.4.149.195/32 fengcheng APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

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

NIC Handles

AC1591-AP AC1718-AP CG272-AP CG272-AP MAINT-CHINANET-SH MAINT-CNCGROUP-GD MZ929-AP MZ929-AP WY2138-AP WY2138-AP YKS16-AP YKS16-AP +2 more