LIANYUNGANG-TELECOM-HAOBAI-DEPT
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 43 blocks across 35 clusters |
| Cluster ID | 206598335 |
| 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.92.27.44/30 | LIANYUNGANG-TELECOM-HAOBAI-DEPT | APNIC | ASSIGNED NON-PORTABLE | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “LIANYUNGANG TELECOM” — 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.
- LIANYUNGANG-TELECOM 5 blocks
- LIANYUNGANG-TELECOM-COMPUTER 2 blocks
- LIANYUNGANG-TELECOM-ZHENHAI 2 blocks
- LIANYUNGANG-TELECOM-LONGHE 2 blocks
- LIANYUNGANG-TELECOM-ENGINEERING 2 blocks
- LIANYUNGANG-TELECOM-NETWORK-DEPT 1 blocks
- LIANYUNGANG-TELECOM-HZ 1 blocks
- LIANYUNGANG-TELECOM-EDU-DEPT 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.
- LIANYUNGANG-TELECOM-MULTIDEMDIA via No.31,Jin-rong Street sub-allocation
- LIANYUNGANG-TELECOM-ZONGDIA-DEPT via No.31,Jin-rong Street sub-allocation
- LIANYUNGANG-TELECOM-11FLOOR-DEPT via No.31,Jin-rong Street sub-allocation
- LIANYUNGANG-TELECOM-HUANGYE-DEPT via No.31,Jin-rong Street sub-allocation
- LIANYUNGANG-TELECOM-ICT-DEPT via No.31,Jin-rong Street sub-allocation
- LIANYUNGANG-TELECOM-DAKEHU-DEPT via No.31,Jin-rong Street sub-allocation
- LIANYUNGANG-TELECOM-ZENGZHI-DEPT via No.31,Jin-rong Street 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
CH451-AP
CH451-AP
MAINT-CHINANET-JS