RCOM
Cluster stats
| Netblocks | 18 |
| All fragments | 185 blocks across 44 clusters |
| Cluster ID | 191529623 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 6 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 59.154.136.92/30 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 115.255.192.0/18 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.0.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.16.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.32.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.48.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.64.0/19 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.96.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.112.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.128.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.144.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.160.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.176.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.192.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.208.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.224.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.125.240.0/20 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 220.224.128.0/18 | RCOM | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: B
how networks compare →
94.4%
of checked blocks have valid RPKI ROA coverage
(17 of 18)
RPKI-inferred operator
Reliance Communications Limited
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
AH406-AP
AH406-AP
MAINT-IN-SN
MAINT-OPTUSCOM-AP
OA3-AP
OA3-AP