Sui Network Resolves Three Outages With Major Upgrade

What Happened

The Sui Network experienced three separate outages between Thursday and Friday, with the blockchain remaining offline for more than 15 hours combined. The first outage lasted nearly six hours on Thursday, followed by two additional incidents on Friday—one lasting eight hours and 25 minutes, and another lasting 43 minutes, according to the network's uptime dashboard.

The Sui Foundation, the nonprofit organization overseeing the Sui Network, deployed a major upgrade on Sunday to address the underlying technical issues. The foundation confirmed that all systems returned to operational status as of Monday.

Key Details

The root causes of the outages have been identified. The first two outages were triggered by bugs introduced in the Sui 1.72 update, according to the Sui Foundation's blog post. The third outage was caused by an interim fix that had been deployed to restore the blockchain following the earlier failures.

Beyond the immediate fixes, the foundation flagged additional areas requiring improvement, including better failure containment mechanisms. The foundation did not specify which validator nodes or operational components were directly affected, nor did it provide detailed technical specifications of the bugs.

Why It Matters

Network outages of this magnitude directly impact user confidence and operational reliability. Extended downtime affects all participants on the blockchain—developers, validators, users, and applications built on Sui. The cascading nature of these outages—where a fix itself triggered a new failure—highlights systemic vulnerabilities in the network's deployment and testing protocols.

For the broader Sui ecosystem, network stability is critical to attracting institutional use and maintaining developer activity. Outages create operational risks for decentralized applications, traders, and staking participants relying on continuous network availability.

What Happens Next

Readers should monitor whether the Sui Foundation implements the failure containment improvements it flagged in its Sunday announcement. The foundation has not disclosed a timeline for these additional enhancements.

The network's performance in the coming weeks will be significant—observers should watch for any further outages or operational anomalies. The foundation may also provide additional technical documentation explaining the specific nature of the bugs in the 1.72 update and how the major upgrade prevents similar issues.

Stakeholders should track any changes to the network's upgrade and testing procedures to prevent future cascading failures.