COOPER-PARRY

BGP inherited
Cluster stats
Netblocks6 · 571 IPv4 addresses
Cluster ID208840642
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.252.145.136/29 COOPER-PARRY RIPE ASSIGNED PA ● low
62.255.9.40/29 COOPER-PARRY RIPE ASSIGNED PA ● low
194.130.218.0/23 COOPER-PARRY RIPE ASSIGNED PA ● low
194.168.99.0/27 COOPER-PARRY RIPE ASSIGNED PA ● low
212.250.119.240/28 COOPER-PARRY RIPE ASSIGNED PA ● low
2a00:2381:ff58::/48 COOPER-PARRY RIPE AGGREGATED-BY-LIR ● low

Possibly related to this organisation

what's this?
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: B how networks compare →
83.3% of checked blocks have valid RPKI ROA coverage (5 of 6)
Possible discrepancies (1)

These blocks are registered to COOPER-PARRY 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:ff58::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AS1849-MNT AS5089-MNT BTNET-MNT DUMY-RIPE DUMY-RIPE