Sui’s mainnet suffered three separate outages across May 28 and 29, halting block production for more than 15 hours and putting fresh pressure on the network’s reliability narrative. The Sui Foundation traced the incidents to defects introduced in the v1.72 software release, including a gas-charging bug and a separate validator randomness issue during an epoch change.
The downtime quickly moved from a technical incident to a market event. SUI fell roughly 19% over the week, while about $1.88 million in long positions were liquidated across the three halts, reinforcing concerns about whether aggressive feature rollouts are being tested deeply enough before reaching production.
Gas Logic Bug Triggers Validator Failures
The first two interruptions stemmed from a flaw in gas-charging logic added with the v1.72 release. The update introduced an address-balance check that caused the system to attempt deductions before transactions were fully validated or rejected for insufficient funds, creating underflow conditions and negative balances.
Those state inconsistencies caused validator crashes and stopped block production for nearly six hours in the first outage. A second halt the following day extended downtime by more than eight hours as teams worked to stabilize validators, restart nodes and deploy corrective patches.
A third disruption came from a different source. The Foundation attributed that halt to a low-probability validator randomness issue during an epoch transition, showing that the upgrade cycle had introduced more than one failure mode.
Together, the incidents exposed how new feature logic can interact with consensus-critical processes in unexpected ways. The problem was not only the presence of bugs, but the fact that those bugs were able to cascade into network-wide halts.
Reliability Becomes the Institutional Test
The outages had a direct market impact. SUI moved from about $0.99 to $0.88 over the week, while forced long liquidations reached approximately $1.88 million. For traders, the episode showed that network downtime can become immediate execution and liquidation risk.
For developers, custodians and institutional users, the concern is broader. Systems that depend on steady block production need confidence that upgrades will not interrupt transaction settlement, collateral management or user access.
The immediate fixes focused on validator crashes and state-consistency problems tied to the gas logic changes. Short-term containment required node restarts and software patches, but the longer-term issue is release governance.
Sui’s next credibility test will be whether the Foundation can demonstrate a stronger upgrade process. That likely means extended integration testing, targeted audits of gas and epoch-transition logic, and better failure isolation before new code can affect the full validator set.
The outages do not end Sui’s institutional ambitions, but they raise the bar for proof. Restoring confidence will require durable fixes, clearer post-mortems and evidence that future software defects can be contained before they halt the network.
