Sui Network Resolves Two-Hour Outage Caused by Bug in Transaction Scheduling Logic

The network went offline, halting new block production and leaving decentralized applications (dApps) on the Sui blockchain inaccessible during the downtime.

Layer 1 blockchain Sui Network, developed by Mysten Labs, encountered a two-hour outage on March 10th. The issue stemmed from a bug in the transaction scheduling logic, causing validator crashes and halting new block production on the network.

The outage rendered decentralized applications (dApps) on the Sui blockchain inaccessible during the downtime. While the blockchain stalled, the team swiftly deployed a patch (v1.37.4) to Mysten Validators to resolve the issue.

After the rollout, the team confirmed that the problem had been fixed and the network was back up. The status page now indicates that “all systems are operational.”

During the宕机, the SUI token dropped nearly 10% to trade at around $3.42, with its market cap currently at $9.8 billion. The token is ranked 18th by market capitalization.

This marks the first major validator-related issue since the Sui mainnet launched in May 2023. However, there was a prior outage in July 2024, when public remote procedure call (RPC) nodes failed to process transactions, and another testnet-related issue earlier this month.

Mysten Labs, the team behind Sui Network, has raised over $336 million in funding to date, with major backing from a16z Crypto, Coinbase Ventures, Binance Labs, and Circle Ventures. Despite these disruptions, Sui continues to attract attention and investment, having been valued at over $2 billion following its $300 million Series B round in 2022.

Several exchanges, including Upbit, suspended SUI transactions during the downtime. However, the network has since resolved the issue and operations have resumed.

Blockchain outages can occur for various reasons, including 51% attacks, issues with nodes (entities that process transactions), or software bugs. In this case, the Sui team identified a bug in the scheduling logic that caused the failure, leading to the disruption of normal network operations.