C@P CONNEXION
FR-CAP-CONNEXION
BGP inherited
Cluster stats
Netblocks7
All fragments 519 blocks across 139 clusters
Cluster ID192850977
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
7 0 netblocks since 2026-07-05
2026-07-05 peak 7 2026-07-06

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
89.185.163.0/24 FR-CAP-CONNEXION RIPE ASSIGNED PA ● low
89.185.164.0/22 FR-CAP-CONNEXION RIPE ASSIGNED PA ● low
89.185.168.0/21 FR-CAP-CONNEXION RIPE ASSIGNED PA ● low
89.185.176.0/20 FR-CAP-CONNEXION RIPE ASSIGNED PA ● low
178.18.176.0/21 FR-CAP-CONNEXION RIPE ASSIGNED PA ● low
178.18.184.0/21 FR-CAP-CONNEXION RIPE ASSIGNED PA ● low
2a00:b280::/34 FR-CAP-CONNEXION RIPE ALLOCATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)
RPKI-inferred operator Radware Ltd
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

CAP-CONNEXION-MNT DUMY-RIPE DUMY-RIPE