K-Opticom
Cluster stats
| Netblocks | 19 |
| All fragments | 20 blocks across 2 clusters |
| Cluster ID | 192268619 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 | |
IP Ranges (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 58.70.0.0/16 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 58.188.0.0/14 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 59.190.0.0/16 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 60.56.0.0/15 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 101.140.0.0/14 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 103.84.124.0/22 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 112.68.0.0/14 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 119.228.0.0/14 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 121.80.0.0/13 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 122.100.24.0/21 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 128.22.0.0/16 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 128.27.0.0/16 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 180.144.0.0/14 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 182.164.0.0/14 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 202.8.48.0/20 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 202.60.32.0/20 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 203.175.80.0/20 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 218.251.0.0/17 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
| 219.75.128.0/17 | K-Opticom | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
89.5%
of checked blocks have valid RPKI ROA coverage
(17 of 19)
RPKI-inferred operator
OPTAGE Inc.
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
JNIC1-AP
JNIC1-AP
MAINT-JPNIC