Ethereum experienced a rare slashing event on Wednesday, with 39 validators penalized, according to blockchain explorer Beaconcha.in.

The validators were tied to the SSV Network, a distributed validator technology (DVT) protocol that decentralizes staking infrastructure by splitting validator keys across multiple operators.

Despite the scale of the incident, SSV founder Alon Muroch emphasized that the protocol itself was not compromised. Instead, the penalties stemmed from operator-side infrastructure issues involving third-party staking providers using SSV.

One cluster of slashed validators was tied to Ankr, a liquid staking provider. According to Muroch, routine maintenance on Ankr’s systems triggered the event. A second slashing involved a validator cluster that had migrated from Allnodes two months earlier. Investigators believe a secondary validator setup caused the duplicate signing that led to penalties.

In total, 39 validators were slashed, making this one of the largest correlated slashing events since Ethereum’s transition to proof-of-stake. Each validator slashed faces an immediate ETH penalty and could face inactivity leaks, compounded losses. One validator, backed by a 2,020 ETH stake, lost around 0.3 ETH, or about $1,300 at today’s prices, in the process.

While slashing is built into Ethereum’s design as a deterrent against malicious or negligent behavior, it remains exceedingly rare. Fewer than 500 validators out of more than 1.2 million active have been slashed since the Beacon Chain went live in 2020. Most incidents, including this one, have been traced to operator issues rather than deliberate attacks.

Mass slashings are particularly notable because correlated misbehavior increases the severity of penalties. Ethereum’s protocol enforces additional inactivity leaks when groups of validators are slashed together, amplifying the financial impact.

For Ethereum’s staking ecosystem, the latest wave underscores a familiar but critical lesson: validator safety hinges as much on infrastructure and operator diligence as on the protocol itself. Even when the underlying software is uncompromised, operational errors can have costly and very public consequences.

Read more: ‘Keep It Simple’: Prevent Your Eth 2.0 From Being Slashed