Sui Faces Second Major Outage Less Than 24 Hours After…

Why Did Sui Stop Processing Blocks Again?

Sui experienced a second major network disruption in less than 24 hours after issues tied to its latest 1.72 software release interrupted block production and forced validators to coordinate another fix. The layer-1 blockchain was offline for 5 hours and 55 minutes on Thursday after what the team described as a bug in gas charging logic introduced by the 1.72 release. Less than a day later, the network suffered another stall on Friday, temporarily pausing activity again before normal block production resumed. “Sui mainnet is currently experiencing a network stall. Network activity may be paused at this time,” the Sui team said on X. “The Sui Core team is actively investigating. Updates and incident review will be shared as soon as they are available.” The last block before Friday’s disruption was produced at about 11:51 UTC, according to block explorer data. Network activity resumed at about 3:30 UTC after the long-term software fix was implemented by a majority of validators.

What Went Wrong With The 1.72 Release?

The disruption centered on the interaction between new address balance functionality and gas charging logic in the 1.72 release. Sui said Thursday’s halt was caused by a crash bug in the gas charging logic, while Friday’s incident was tied to the interim fix that had been deployed to restore network functionality. “Both today’s and yesterday’s halts are due to the interaction of the 1.72 release, which introduced address balances and gas charging logic. Yesterday’s implemented fix was an interim measure designed to restore functionality to the network,” the Sui team said. The team said the interim fix had a low probability of causing another disruption. That risk materialized on Friday, forcing validators to move to the longer-term software fix. At least two-thirds of the validator set had already upgraded to the Thursday fix before the second issue appeared. The 1.72.2 release introduced 2 major protocol additions: Address Balances and Gasless Stablecoin Transfers. Address Balances were designed to simplify transactions by moving away from Sui’s UTXO-style model and adding a single canonical balance for each token type. Gasless Stablecoin Transfers were designed to let supported stablecoins move peer-to-peer without gas fees or a separate gas token.

Investor Takeaway

Sui’s outages show the risk of shipping core protocol upgrades that touch balances, gas logic, and transaction execution. The market issue is not only downtime, but whether developers, exchanges, and stablecoin users can rely on the network during major releases.

Why Do Repeated Outages Matter For Sui?

Friday’s stall came after Sui’s worst outage on record and followed another major disruption in January. In that earlier incident, the network went offline for more than 6 hours after a consensus bug prevented validators from reaching the required threshold to continue block production. The January post-mortem said validators submitted conflicting transactions to the checkpoint mechanism, causing the network to halt. Sui said at the time that the issue was not caused by congestion, user funds were never at risk, and no certified transactions were rolled back. The latest incidents create a different concern because they were tied to a live software upgrade. The 1.72 release was meant to support simpler balances and gasless stablecoin transfers, both of which are commercially important for user experience and payments adoption. When features aimed at improving usability trigger outages, the chain faces a credibility test with developers and liquidity providers. The SUI token traded around $0.90 during the disruption, down slightly on the day. The limited price reaction suggests traders did not treat the outage as a full confidence break, but repeated network stalls can weigh on longer-term adoption if they continue.

What Are The Broader Market Implications?

High-throughput smart contract networks have more technical pressure points than simpler blockchain systems. Transaction execution, validator consensus, data availability, gas accounting, and state management all have to work together under real network conditions. A bug in one layer can stop the whole system if validators cannot safely continue. For Sui, the immediate task is to publish a full incident review and show that the long-term fix has removed the issue introduced by the 1.72 release. The bigger task is proving that future upgrades can be deployed without forcing repeated validator coordination during live market hours. The outages also matter for exchanges and service providers. When a layer-1 blockchain stops producing blocks, deposits, withdrawals, on-chain settlement, DeFi activity, and bridge operations can all be paused. That can create operational risk beyond the chain itself, especially for assets used across trading venues and wallets. Sui’s development roadmap depends on performance, consumer applications, and payments-related features such as gasless stablecoin transfers. Those ambitions require network reliability as much as speed. The latest stalls do not end Sui’s growth case, but they make uptime and release management the central tests for the chain’s next phase.