JIMEI

BGP inherited
Cluster stats
Netblocks7
All fragments 21 blocks across 13 clusters
Cluster ID208844299
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 15 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
114.251.135.216/30 JIMEI APNIC ASSIGNED NON-PORTABLE ● high
116.236.202.164/30 JIMEI APNIC ASSIGNED NON-PORTABLE ● high
123.124.214.152/29 JIMEI APNIC ASSIGNED NON-PORTABLE ● high
180.168.209.152/30 JIMEI APNIC ASSIGNED NON-PORTABLE ● high
58.252.73.35/32 jimei APNIC ASSIGNED NON-PORTABLE ● low
58.252.73.41/32 jimei APNIC ASSIGNED NON-PORTABLE ● low
58.252.73.43/32 jimei APNIC ASSIGNED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “JIMEI” — 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 13 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.

Network trust

what's this?
RPKI hygiene: C how networks compare →
57.1% of checked blocks have valid RPKI ROA coverage (4 of 7)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP AC1718-AP CG272-AP CG272-AP HP489-AP HP489-AP MAINT-CHINANET-SH MAINT-CNCGROUP-BJ MAINT-CNCGROUP-GD MZ907-AP MZ907-AP SJ272-AP +3 more