MAINT-CHINANET-HA
BGP inherited
Cluster stats
| Netblocks | 2 · 327,678 IPv4 addresses |
| All fragments | 3 blocks across 2 clusters |
| Cluster ID | 206539206 |
| 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 123.52.0.0/14 | MAINT-CHINANET-HA | APNIC | ALLOCATED PORTABLE | ● low |
| 123.101.0.0/16 | MAINT-CHINANET-HA | APNIC | ALLOCATED PORTABLE | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MAINT CHINANET” — 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.
- MAINT-CHINANET-GS 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.
- MAINT-CHINANET-GS 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
(2 of 2)
RPKI-inferred operator
No.31,Jin-rong Street
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
AC1573-AP
APNIC-HM
HZ149-AP
HZ149-AP