The Sui blockchain suffered three complete mainnet halts in under 48 hours, from May 28 to 29, 2026. What makes this incident particularly striking is that the team knowingly caused one of those halts themselves — developers admitted they deployed an interim fix with a recognized risk of triggering another outage. It happened exactly as warned.
What Happened
On May 28, at approximately 7:00 a.m. PT, Sui's mainnet went down. The cause was a bug in the v1.72 upgrade related to "gas smashing" — a mechanism that combines input coins into a single coin to pay transaction fees. The first halt lasted until around 1:30 p.m. PT. But the underlying issue remained.
To restore the network quickly, the team deployed an interim fix that they openly acknowledged carried "a known issue with a low probability of causing a halt." They accepted that risk. The next morning, the mainnet halted again — for exactly the reason developers had already flagged internally. Three halts in 48 hours total.
Why It Matters
Sui has been one of the fastest-growing blockchains in recent years, positioning itself as a high-performance platform for DeFi and gaming. Three sequential failures aren't a random bug — they point to a systemic issue. This is already the third major reliability incident since the mainnet launched in 2023.
Most concerning is the team's deliberate decision to accept a known risk. When speed of recovery is prioritized over stability, application developers and users end up bearing the consequences of others' trade-offs.
Market and Ecosystem Impact
The SUI token lost around 19% over the course of the week. No user funds were lost and no transactions were reversed — but hours-long outages carry real costs for protocols, trading platforms, and developers building on Sui.
- First halt: approximately 6 hours (May 28)
- Second halt: approximately 5 hours (May 28–29)
- Third halt: morning of May 29 — triggered by the known bug in the interim fix
- SUI price drop: approximately 19% over the week
What Comes Next
The Sui team released a final fix and published a postmortem. They acknowledged the flaw in the interim patch and committed to revising upgrade testing procedures before future mainnet deployments.
For developers and users in the Sui ecosystem, this is a clear signal: infrastructure risk is real. Building resilience into protocols and maintaining sound asset management isn't paranoia — it is prudent engineering practice.
