MECAPLAST

BGP inherited
Cluster stats
Netblocks7
Registered in France (6) · Switzerland (1)
All fragments 9 blocks across 3 clusters
Cluster ID208958704
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (7)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.146.221.24/29 MECAPLAST-NET RIPE ASSIGNED PA ● low
83.169.77.80/29 MECAPLAST RIPE ASSIGNED PA ● low
86.65.150.60/30 MECAPLAST RIPE ASSIGNED PA ● low
109.3.130.120/30 MECAPLAST RIPE ASSIGNED PA ● low
109.3.130.192/28 MECAPLAST RIPE ASSIGNED PA ● low
194.183.195.4/30 MECAPLAST RIPE ASSIGNED PA ● low
194.183.220.156/30 MECAPLAST RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “MECAPLAST” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
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 →
85.7% of checked blocks have valid RPKI ROA coverage (6 of 7)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE EEF-MNT INTFR-MNT LDCOM-MNT LDCOM-PRO-MNT SIRIS-MNT