AIC-SHENZHEN-FUTIAN-DISTRICT
BGP inherited
Cluster stats
| Netblocks | 10 |
| All fragments | 11 blocks across 2 clusters |
| Cluster ID | 208795440 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 21 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
10
0 netblocks since 2026-07-05
2026-07-05
peak 10
2026-07-19
IP Ranges (10)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 61.144.239.60/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.211.16/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.212.224/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.212.228/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.212.232/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.212.236/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.212.244/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.213.212/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.213.216/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 218.17.213.224/30 | AIC-SHENZHEN-FUTIAN-DISTRICT | APNIC | ASSIGNED NON-PORTABLE | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “AIC SHENZHEN” — 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.
- AIC-SHENZHEN-LUOHU-DISTRICT 1 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.
- shenzhentaidugu-com via CNCGROUP IP network of ShangHai IDC sub-allocation
- Hai Kou Shen Zhen Fa Zhan Bank via CNCGROUP IP network of ShangHai IDC sub-allocation
- shenzhen-qinhai-gongsi sub-allocation
- Shenzhen Ying Tong intelligence community network Co LTD sub-allocation
- Chuang Xin trading Shanghai Co LTD shenzhen branch via China Unicom sub-allocation
- Information-Technology-Co-Ltd-Shenzhen-Invensys via China Unicom sub-allocation
- Peng Da Chuan Wu Shen Zhen You Xian Go via CNCGROUP IP network of ShangHai IDC sub-allocation
- Shen Zheng Xin Zhong Nan 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
(10 of 10)
No discrepancies found among checked blocks.
NIC Handles
HQ33-AP
HQ33-AP
HQS10-AP
HQS10-AP
HQS2-AP
HQS2-AP
HQS3-AP
HQS3-AP
HQS4-AP
HQS4-AP
HQS5-AP
HQS5-AP
+9 more