Skip to content
- Sui Mainnet suffered three outages on May 28 and 29, 2026.
- Two incidents came from a gas payment bug, while the third involved validator randomness.
- Developers fixed the issues and restored the network without any loss of user funds.
According to the blog, Sui Mainnet faced three separate outages on May 28 and 29, 2026, after software bugs disrupted network operations. The incidents temporarily halted transaction processing and forced developers and validators to implement emergency fixes.
Despite the interruptions, the network protected user funds and preserved all confirmed transactions. The first outage started on Thursday morning and lasted several hours. A second disruption followed on Friday morning, while a third halt occurred later that afternoon. After a series of fixes and validator upgrades, normal network activity resumed.
Address Balance Feature Causes Sui Network Issues
The initial two outages were due to a problem associated with the newly added address balance functionality as part of the Sui 1.72 upgrade. This is an innovation that enables customers to pay for transactions by using their address balance instead of being limited to coin objects.
In some instances, there had been simultaneous usage of the same balance by multiple transactions. In such instances, where the available funds were inadequate to support all transactions, one was stopped automatically. This was due to a discrepancy in the gas-processing mechanism, leading to a failure of the balance calculation and subsequent crashing of the validator nodes.
Temporary steps were taken by the developers to ensure stability on Thursday, allowing work to continue towards fixing the problem permanently. However, the problem resurfaced on Friday in a new form, but developers managed to provide another remedy.
Randomness Failure Triggers Third Outage
The third outage came about as a result of yet another problem associated with software, which emerged during an epoch transition which was to take place on Friday afternoon. Before every epoch begins, the validators initiate the key generation process in a decentralized manner, a process that contributes towards the production of randomness on the blockchain. With regard to previous restarts, the participation rate had not been enough to trigger this process.
The randomness feature for this epoch was successfully deactivated. However, due to another bug in the system, once the validators restarted, the system could not store this information. The validators consequently thought that randomness was still active and thus could not proceed.
The bug has been solved by developers and a solution has been put in place such that the validators have completed this epoch and continue progressing through the network.
Also Read: Ancient Bitcoin Whale Sends $203M BTC to Trading Firms, Traders Alarmed
