RMNI-JP
Cluster stats
| Netblocks | 4 |
| Cluster ID | 191770581 |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.124.0.0/24 | RMNI-JP | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 103.124.1.128/26 | RMNI-JP | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 103.124.2.0/23 | RMNI-JP | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 193.114.32.0/21 | RMNI-JP | 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
(4 of 4)
Possible discrepancies (3)
These blocks are registered to RMNI-JP but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 193.114.32.0/21 /21 | authorized for AS138384 — Rakuten Mobile, Inc. |
| 103.124.2.0/23 /23 | authorized for AS138384 — Rakuten Mobile, Inc. |
| 103.124.0.0/24 /24 | authorized for AS138384 — Rakuten Mobile, Inc. |
NIC Handles
AR792-AP
MAINT-RMNI-JP
RMNI1-AP
RMNI1-AP