OWL-JP-01
Unresolved
Cluster stats
| Netblocks | 2 |
| All fragments | 3 blocks across 2 clusters |
| Cluster ID | 194501186 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.88.46.0/24 | OWL-JP-01 | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 103.125.234.0/24 | OWL-JP-01 | APNIC | ALLOCATED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (2)
These blocks are registered to OWL-JP-01 but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 103.88.46.0/24 /24 | authorized for AS4785 — xTom Limited |
| 103.125.234.0/24 /24 | authorized for AS3258 — xTom Japan Corporation |
NIC Handles
AO228-AP
MAINT-OWL-VU
OLA15-AP
OLA15-AP