JUREN

BGP inherited
Cluster stats
Netblocks8
All fragments 22 blocks across 4 clusters
Cluster ID209183200
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 18 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
116.228.152.104/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high
116.236.238.64/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high
116.236.238.128/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high
116.236.238.136/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high
116.236.238.144/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high
116.236.238.152/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high
116.236.238.160/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high
222.66.162.216/29 JUREN APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “JUREN” — 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.
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP MAINT-CHINANET-SH ZT436-AP ZT436-AP ZT438-AP ZT438-AP ZT439-AP ZT439-AP ZT440-AP ZT440-AP ZT441-AP ZT441-AP +6 more