JUNSI

BGP inherited
Cluster stats
Netblocks7
Cluster ID210250069
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 16 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
116.236.162.60/30 JUNSI APNIC ASSIGNED NON-PORTABLE ● high
116.236.185.76/30 JUNSI APNIC ASSIGNED NON-PORTABLE ● high
180.168.82.144/30 JUNSI APNIC ASSIGNED NON-PORTABLE ● high
180.168.94.108/30 JUNSI APNIC ASSIGNED NON-PORTABLE ● high
180.169.88.4/30 JUNSI APNIC ASSIGNED NON-PORTABLE ● high
218.80.210.104/30 JUNSI-CO APNIC ASSIGNED NON-PORTABLE ● high
222.66.239.168/30 JUNSI-CO APNIC ASSIGNED NON-PORTABLE ● high

Possibly related to this organisation

what's this?
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 (7 of 7)
No discrepancies found among checked blocks.

NIC Handles

AC1591-AP MAINT-CHINANET-SH ML1336-AP ML1336-AP ML1565-AP ML1565-AP ML1578-AP ML1578-AP ML1678-AP ML1678-AP ML1679-AP ML1679-AP +4 more