SACMI
BGP inherited
Cluster stats
| Netblocks | 13 |
| All fragments | 45 blocks across 30 clusters |
| Cluster ID | 205577709 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 | |
Footprint over time
4 weekly snapshots · JSON
13
0 netblocks since 2026-07-05
2026-07-05
peak 13
2026-07-13
IP Ranges (13)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 77.252.112.64/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.0/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.8/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.16/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.24/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.32/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.40/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.48/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.56/29 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.64/28 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.80/28 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.96/28 | SACMI | RIPE | ASSIGNED PA | ● low |
| 213.209.201.112/28 | SACMI | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “SACMI” — 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.
- SACMI-IPREL 2 blocks
- SACMI_PACKAGING_CHOCOLATE 2 blocks
- SACMI-SG 2 blocks
- SACMI_MOLDS_AND_DIES 1 blocks
- SACMI_VERONA 1 blocks
- SACMI-CARPMEC 1 blocks
- SACMI-BMR 1 blocks
- SACMI_TECH 1 blocks
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.
- SACMIIBERICASA via TELEFONICA DE ESPANA S.A.U. sub-allocation
- SACMI-ACANTHO via HERABIT S.p.A. sub-allocation
- SACMICOOPERATIVAMECCANICIIMOLASOCIETACOOPERATIVAINB sub-allocation
- SACMI_MOLDS_AND_DIES via HERABIT S.p.A. sub-allocation
- SACMI_TECH via HERABIT S.p.A. sub-allocation
- SACMI_VERONA via HERABIT S.p.A. sub-allocation
- SACMI-CARPMEC via HERABIT S.p.A. sub-allocation
- SACMI-BMR via HERABIT S.p.A. sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(13 of 13)
No discrepancies found among checked blocks.
NIC Handles
CASAWEB-MNT
DUMY-RIPE
DUMY-RIPE
NETIA-MNT