CNCGROUP IP network of ShangHai IDC

NP-puchen-hongzhengli-gongs

BGP inherited

Cluster stats

Netblocks	1
All fragments	21 blocks across 21 clusters
Cluster ID	206890369
Registry	APNIC
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 4 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
220.249.150.197/32	NP-puchen-hongzhengli-gongs	APNIC	ASSIGNED NON-PORTABLE	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “NP puchen” — 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.

Combined view of all 21 name-family clusters →

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.

LANPUCHENG-MATERIAL-COM via CNCGROUP IP network of ShangHai IDC sub-allocation
Pucheng Tianbao via CNCGROUP IP network of ShangHai IDC sub-allocation
Puchen Suishan via CNCGROUP IP network of ShangHai IDC sub-allocation
Puchen Baiyan via CNCGROUP IP network of ShangHai IDC sub-allocation
Puchen Junyi via CNCGROUP IP network of ShangHai IDC sub-allocation
Puchen Jiaobanzhan via CNCGROUP IP network of ShangHai IDC sub-allocation
Puchengnan Shoufeizhan via CNCGROUP IP network of ShangHai IDC sub-allocation
Puchen Qiangui Ktv 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 (1 of 1)

No discrepancies found among checked blocks.

NIC Handles

AC1718-AP MAINT-CN-NP28 NP118-AP NP118-AP