CPMS
Cluster stats
Netblocks10
All fragments 11 blocks across 2 clusters
Cluster ID192185184
RegistryRIPE
Customersfind 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 (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
87.236.24.0/26 CPMS RIPE ASSIGNED PA ● low
87.236.24.64/26 CPMS RIPE ASSIGNED PA ● low
87.236.24.128 – 87.236.24.239 CPMS RIPE ASSIGNED PA ● low
87.236.25.0/24 CPMS RIPE ASSIGNED PA ● low
87.236.26.0/24 CPMS RIPE ASSIGNED PA ● low
87.236.27.0/24 CPMS RIPE ASSIGNED PA ● low
87.236.28.0/24 CPMS RIPE ASSIGNED PA ● low
87.236.29.0/24 CPMS RIPE ASSIGNED PA ● low
87.236.30.0/23 CPMS RIPE ASSIGNED PA ● low
2a00:2381:8::/48 CPMS RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
Possible discrepancies (7)

These blocks are registered to CPMS 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.

2a00:2381:8::/48 /48 authorized for AS2856 — British Telecommunications PLC
87.236.30.0/23 /23 authorized for AS12714 — PJSC MegaFon
87.236.26.0/24 /24 authorized for AS12714 — PJSC MegaFon
87.236.27.0/24 /24 authorized for AS12714 — PJSC MegaFon
87.236.29.0/24 /24 authorized for AS12714 — PJSC MegaFon
87.236.25.0/24 /24 authorized for AS12714 — PJSC MegaFon
87.236.28.0/24 /24 authorized for AS12714 — PJSC MegaFon

NIC Handles

BTNET-MNT DUMY-RIPE DUMY-RIPE TI-MNT