China Unicom
SHANG-HAI-XIN-FANG-ZHI-NEN-XI-TONG
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 3 blocks across 2 clusters |
| Cluster ID | 206411791 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 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 |
|---|---|---|---|---|
| 218.244.250.112/28 | SHANG-HAI-XIN-FANG-ZHI-NEN-XI-TONG | APNIC | ASSIGNED NON-PORTABLE | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “SHANG HAI XIN FANG ZHI” — 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.
- SHANG-HAI-XIN-FANG-ZHI-NENG-XI-TONG 2 blocks
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.
- WAN-FANG-SHANG-WANG via China Unicom sub-allocation
- FANG-YUAN-DA-SHA-SHANG-WU-LOU sub-allocation
- Com via CNCGROUP IP network of ShangHai IDC sub-allocation
- shangfang-mansion sub-allocation
- shanghai-xinyi-fangwu sub-allocation
- shanghai-jinjia-fangdichan sub-allocation
- shanghai-huatian-fangdichan 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
MAINT-CNNIC-AP
PP40-AP
PP40-AP