The Sui network hit a temporary stall over the weekend after the same software bug that triggered a nearly six-hour outage on Thursday came back. Developers said the glitch is tied to a recent network update and that they are working on a permanent fix.
What Caused the Stall
The bug originates in the network update software that Sui uses to roll out changes. On Thursday, that bug took the chain down for almost six hours. This weekend it reappeared, causing another disruption — though this time the stall was shorter and the network recovered on its own, according to the team.
The company hasn't disclosed the exact technical details of the flaw, but noted that it can be triggered during routine software upgrades. Both incidents happened shortly after the same update was deployed.
Impact on Users and Transactions
During the Thursday outage, block production halted completely. Users couldn't send transactions or interact with decentralized applications on Sui. The weekend stall was less severe, but it still interrupted service for a period. The team confirmed that no user funds were lost or compromised in either event.
Transaction data from the period shows a sharp drop in activity during the downtime, followed by a quick recovery once the chain resumed. Validators on the network had to restart some nodes to get things moving again.
Repeated Bug Raises Questions
Two outages from the same underlying cause in less than a week has put Sui's update process under scrutiny. The network, which launched its mainnet last year, has generally been stable until now. Developers say they're testing a more robust patch, but they haven't given a timeline for when it will be deployed.
For now, the team is advising validators to hold off on applying the latest update until a fix is confirmed. That leaves the network running on the same code that has already failed twice.
Whether the bug is fully understood — and whether the upcoming patch will finally eliminate it — are questions that remain open. The next update could arrive within days, but until it's tested on a live network, no one can be sure the problem won't come back a third time.
