What happened
Three downtime incidents caused by errors in fee logic and update 1.72 were resolved by the platform's developers.
Why it matters
Mainnet stability is the foundation of trust for users and developers of decentralized applications. Recurring outages, especially those linked to core protocol updates, highlight the risks associated with deploying new features such as balance management and can temporarily disrupt ecosystem operations.
The Sui blockchain mainnet experienced three instances of operational halts on Thursday, May 28, and Friday, May 29, 2026. According to an official statement from the project team, the first two incidents were caused by critical bugs leading to system crashes.
The failures resulted from incorrect interactions between gas fee logic and features introduced in the recent version 1.72 update, which added support for address balances. Developers promptly released a patch that eliminated the vulnerabilities and restored network stability.
Despite the severity of the technical issues, which led to a complete cessation of transaction processing on the specified dates, the Sui team was able to isolate the source of the errors and complete the recovery process without prolonged infrastructure downtime.
Confirmed facts
- The Sui mainnet experienced three downtime incidents on May 28 and 29, 2026.
- The first two failures were caused by bugs leading to system crashes.
- The errors arose from the interaction between gas fee logic and the version 1.72 release.
- Update 1.72 implemented the address balances feature.
- The incidents were resolved following the release of patches.
Context
Information is based exclusively on the official Sui blog post published on May 31, 2026. At the time of publication, there are no independent confirmations or detailed technical reports from third-party auditors regarding the specific conditions under which these bugs occurred.
What remains unknown
- What were the exact technical conditions that triggered the interaction of errors in the gas logic?
- Were user funds affected, or did only transaction processing halt?
- Are additional code audits planned before future major updates?
AI analysis
Confidence: medium
Analysis of the situation indicates the complexity of integrating new economic models (address balances) into the existing transaction execution architecture. The fact that several attempts were required to fully stabilize the system after the initial release suggests a high degree of interconnectivity among system components, where a change in one module triggers cascading effects in others.
Strategic AI conclusion
The most likely consequence will be intensified internal protocol testing prior to future hard forks. The next observable signal will be the publication of a detailed post-mortem containing technical specifics of the vulnerabilities. A key uncertainty remains the impact of these events on the platform's reputation among institutional investors, who are sensitive to uptime.