NIDEC-SANKYO

Handle
Cluster stats
Netblocks7 · 110,585 IPv4 addresses
All fragments 9 blocks across 2 clusters
Cluster ID210114909
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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

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
160.21.0.0/18 NIDEC-SANKYO APNIC ASSIGNED PORTABLE ● high
160.21.0.0/16 NIDEC-SANKYO APNIC ASSIGNED PORTABLE ● high
160.21.80.0/20 NIDEC-SANKYO APNIC ASSIGNED PORTABLE ● high
160.21.96.0/21 NIDEC-SANKYO APNIC ASSIGNED PORTABLE ● high
160.21.128.0/20 NIDEC-SANKYO APNIC ASSIGNED PORTABLE ● high
160.21.160.0/21 NIDEC-SANKYO APNIC ASSIGNED PORTABLE ● high
160.21.192.0/18 NIDEC-SANKYO APNIC ASSIGNED PORTABLE ● high

Possibly related to this organisation

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

NIC Handles

MAINT-JPNIC ON3-AP ON3-AP