DataCenter-Merckel
Cluster stats
| Netblocks | 4 |
| All fragments | 248 blocks across 50 clusters |
| Cluster ID | 192564712 |
| Registry | RIPE |
| Customers | find 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.67.252.0/24 | DataCenter-Merckel | RIPE | ASSIGNED PA | ● high |
| 45.67.253.0/24 | DataCenter-Merckel | RIPE | ASSIGNED PA | ● high |
| 45.67.254.0/24 | DataCenter-Merckel | RIPE | ASSIGNED PA | ● high |
| 45.67.255.0/24 | DataCenter-Merckel | RIPE | ASSIGNED PA | ● high |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (1)
These blocks are registered to DataCenter-Merckel but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 45.67.253.0/24 /24 | authorized for AS59877 — VA TELECOM SAS |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MERCKEL-MNT
mnt-fr-merckel-1