COLACEM

BGP inherited
Cluster stats
Netblocks8
All fragments 9 blocks across 2 clusters
Cluster ID209282191
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
5.154.216.88/29 COLACEM-NET RIPE ASSIGNED PA ● low
5.154.216.100/30 COLACEM-NET RIPE ASSIGNED PA ● low
88.35.153.48/29 COLACEM RIPE ASSIGNED PA ● low
88.44.97.176/28 COLACEM RIPE ASSIGNED PA ● low
88.45.218.168/29 COLACEM RIPE ASSIGNED PA ● low
88.56.56.64/28 COLACEM RIPE ASSIGNED PA ● low
88.56.62.32/29 COLACEM RIPE ASSIGNED PA ● low
88.56.63.96/29 COLACEM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “COLACEM” — 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: D how networks compare →
25.0% of checked blocks have valid RPKI ROA coverage (2 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE INTERB-MNT MNT-CONNESI