ONWATCH PLC
ONWATCH-PLC
Cluster stats
| Netblocks | 20 |
| All fragments | 27 blocks across 8 clusters |
| Cluster ID | 192391533 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (20)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 59.154.156.24/30 | ONWATCH | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 79.123.22.24/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.22.88/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.22.96/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.22.104/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.22.112/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.22.120/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.24.48/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.38.16/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.46.72/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.46.224/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.46.232/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.46.240/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.51.232/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.67.168/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 79.123.67.176/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 80.168.131.16/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 213.253.57.184/29 | ONWATCH-PLC | RIPE | ASSIGNED PA | ● low |
| 2a00:2381:f3d9::/48 | ONWATCH | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:f3d9:100::/56 | ONWATCH-PLC | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(20 of 20)
Possible discrepancies (2)
These blocks are registered to ONWATCH PLC 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.
| 2a00:2381:f3d9::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
| 2a00:2381:f3d9:100::/56 /56 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
AS8426-MNT
BTNET-MNT
DUMY-RIPE
DUMY-RIPE
MAINT-OPTUSCOM-AP
OA3-AP
OA3-AP