The Sui mainnet outage that occurred between May 28 and May 29, 2026, became one of the most significant reliability incidents in the network's history. 

Over the course of two days, the blockchain experienced three separate disruptions that temporarily halted block production, froze approximately $1 billion in on-chain assets, and triggered a sharp decline in the SUI token price.

While no user funds were lost and no transactions were reversed, the incidents raised important questions about network resilience, upgrade testing, and the challenges of maintaining high-performance Layer 1 blockchains. 

The outages were ultimately traced to bugs introduced in the SUI v1.72 software upgrade, exposing unexpected edge cases in the protocol's gas management and randomness systems.

So what exactly happened, why did the SUI network halt multiple times, and what does it mean for users and investors moving forward? Let's break it down.

Key Takeaways

• The Sui mainnet outage was caused by bugs introduced in the SUI v1.72 upgrade, not by hacking, congestion, or security breaches.

• Three separate network halts occurred over May 28–29, 2026, temporarily stopping transaction processing and affecting roughly $1 billion in on-chain assets.

• Although SUI price fell around 8% during the incidents, no funds were lost, and the network fully recovered after coordinated validator upgrades.

Trade with confidence. Bitrue is a secure and trusted crypto trading platform for buying, selling, and trading Bitcoin and altcoins.
Register Now to Claim Your Prize!

What Happened During the Sui Mainnet Outage?

The outage unfolded across three separate incidents within roughly 36 hours.

The first disruption began on May 28 at approximately 7 a.m. PT. Validators entered a crash loop, causing the network to stop producing blocks entirely. As a result, transactions could not be processed, DeFi protocols became effectively frozen, and users were unable to complete on-chain operations.

After developers implemented an interim fix, the network resumed operations. However, a second outage occurred on May 29 around 5 a.m. PT after another variation of the same underlying bug surfaced.

Later that day, a third and final outage occurred between approximately 1:30 p.m. and 7:20 p.m. PT. This incident stemmed from a different issue related to validator restarts and the network's randomness protocol.

Throughout these disruptions, public RPC endpoints still provided read access to blockchain data in certain periods. However, transaction settlement and execution remained unavailable until the network was fully restored.

Eventually, validators upgraded to patched software versions, and once more than two-thirds of staked validators adopted the fixes, the network resumed normal operations.

Read Also: LiquidChain LIQUID: Emerging Layer 3 Crypto to Watch in 2026

What Caused the SUI Network Halts?

The root of the crisis was traced to the v1.72 software upgrade, which introduced a new address-balance mechanism for transaction fee payments.

The upgrade aimed to improve flexibility by allowing users to pay fees using address balances alongside traditional coin objects. However, subtle edge cases emerged that had not been fully detected during testing.

The Gas Logic Bug in SUI v1.72

The first and second outages originated from a protocol-level bug within Sui's gas charging system.

Unlike account-based blockchains, Sui uses an object-centric architecture where balances are represented as individual coin objects. These objects can be merged, split, and managed independently.

The issue occurred when transactions attempted to use a combination of address balances and coin objects for gas payments.

When a transaction was canceled due to insufficient funds, validators incorrectly attempted to continue charging gas fees. This produced an impossible negative balance scenario known as an underflow error.

Once triggered, validators crashed simultaneously, causing the entire network to halt.

An initial emergency patch resolved the most common form of the bug. However, developers were already aware of a low-probability edge case that remained unresolved.

Unfortunately, that edge case triggered the second outage.

In the second incident, a different error condition masked the original insufficient-funds signal, bypassing the interim protection mechanism and causing validators to crash again.

A more comprehensive fix was subsequently deployed to eliminate the vulnerability entirely.

The Randomness Protocol Bug

The third outage emerged from a completely different source.

As validators restarted after applying the robust gas fix, participation in Sui's on-chain randomness protocol temporarily dropped below required thresholds.

The protocol behaved correctly by disabling randomness generation. However, a hidden bug prevented that disabled state from being saved permanently.

When the network reached its next epoch transition, validators incorrectly assumed randomness services were still active. As a result, they waited indefinitely for randomness data that would never arrive.

This stalled the end-of-epoch process and halted the blockchain once again.

Although unrelated to the gas logic issue, the bug demonstrated how multiple complex systems within a blockchain can interact in unexpected ways during upgrade and recovery procedures.

Read Also: What is GITHOOK? GITHOOK Coin Explained and Price Prediction 2026

How Did the Sui Mainnet Outage Affect the SUI Price?

The market reacted quickly to the series of outages.

Before the incidents, SUI was trading near $0.99. As confidence weakened and uncertainty spread throughout the ecosystem, the token dropped approximately 8%, reaching the $0.90–$0.91 range during the disruptions.

The broader weekly decline was even more severe, with SUI falling roughly 19%.

Several factors contributed to the price reaction:

• Concerns about network reliability.

• Temporary disruption of DeFi activity.

• Exchange deposit and withdrawal pauses.

• Reduced investor confidence following repeated outages.

• Increased scrutiny from institutional participants.

Following recovery, price volatility remained elevated as traders evaluated the long-term implications of the event.

Technical analysts identified support levels between $0.85 and $0.88, while resistance zones appeared around $0.95 to $1.00.

Is Sui Safe After the Network Halt?

One of the most common questions following the incident is: Is Sui safe?

From a security perspective, the answer is largely yes.

The outage was not caused by a hack, exploit, validator attack, or malicious activity. It was a software reliability issue triggered by bugs in core protocol logic.

Importantly:

• No user funds were lost.

• No transactions were reversed.

• No chain forks occurred.

• Committed transactions remained valid.

• Network integrity was preserved.

The incident exposed weaknesses in software testing and upgrade deployment rather than vulnerabilities in asset security.

However, reliability remains a critical component of blockchain trust. Even if funds remain secure, prolonged downtime can disrupt trading, liquidations, lending, staking, and other financial activities.

For users and institutions, the key concern moving forward is whether future upgrades can avoid similar disruptions.

Read Also: What Is ARCANE Crypto? Analysing the Investment Opportunity

Ecosystem Impact: DeFi, Exchanges, and Users

The Sui blockchain downtime affected numerous ecosystem participants.

DeFi Protocols

Major DeFi applications experienced temporary disruptions.

Protocols such as Scallop and Cetus faced delayed liquidations, frozen liquidity, and interrupted user activity. Traders could not execute transactions while block production remained paused.

Exchanges

Several cryptocurrency exchanges temporarily suspended SUI deposits and withdrawals to prevent operational complications during the network instability.

While trading markets generally remained active, on-chain settlement was unavailable until recovery.

DApps and Infrastructure Providers

Wallets, explorers, RPC services, and decentralized applications also experienced interruptions.

Although users could often view balances and historical data, they could not complete new transactions until validators restored normal operations.

How Sui Recovered From the Outage

The Sui Foundation and validator community responded rapidly.

Developers diagnosed the root causes, distributed emergency patches, coordinated upgrades, and monitored validator adoption throughout the recovery process.

The response included:

• Deployment of interim fixes.

• Release of permanent protocol patches.

• Coordinated validator upgrades.

• Publication of a detailed post-mortem report.

• Enhanced monitoring procedures.

The Foundation also outlined future improvements, including:

• More resilient end-of-epoch processing.

• Better failure containment mechanisms.

• More modular gas accounting logic.

• Expanded edge-case testing.

• Gradual rollout procedures for future upgrades.

These measures aim to reduce the likelihood that a single software bug could trigger a network-wide halt.

Read Also: Japan Plans to Integrate Bonds with Blockchain for 24 Hour Trading

What the Incident Means for Sui's Future

The May 2026 outages represent an important stress test for Sui.

On one hand, the incidents highlight the risks associated with rapid innovation on high-performance Layer 1 networks. Advanced features often introduce greater complexity, making edge cases harder to identify before deployment.

On the other hand, the response demonstrated several strengths.

The network recovered without asset losses, validators coordinated effectively, and developers provided transparency through detailed technical explanations.

Still, this marks the third major mainnet incident since Sui launched in 2023, following transaction scheduling issues in November 2024 and consensus divergence problems in January 2026.

As Sui continues pursuing growth in DeFi, gaming, institutional finance, and Bitcoin-related applications, reliability will become increasingly important.

The success of future upgrades may ultimately determine whether the market views these outages as temporary growing pains or signs of deeper operational challenges.

How to Trade SUI After the Outage

For traders, the post-outage environment presents both opportunities and risks.

Before entering new positions, consider:

• Monitoring validator and network performance updates.

• Watching key support and resistance zones.

• Evaluating ecosystem activity and TVL recovery.

• Following future upgrade announcements closely.

• Managing risk through proper position sizing.

Historically, crypto assets often experience volatility after major network incidents. While some recover quickly, others require longer periods to rebuild confidence.

As always, conduct your own research before trading SUI or any cryptocurrency. You can explore market insights, trading tools, and the latest SUI developments on Bitrue before making investment decisions.

Conclusion

The Sui mainnet outage of May 2026 was a significant reliability event caused by bugs introduced in the SUI v1.72 upgrade. Three separate network halts disrupted transactions, affected DeFi activity, and contributed to a notable SUI price decline.

Despite the operational impact, no funds were lost, no security breaches occurred, and the network eventually recovered through coordinated validator action and protocol fixes. 

The incident serves as a reminder that blockchain innovation often comes with technical challenges, particularly when introducing complex new features.

For investors and users, the key question is no longer whether Sui survived the outage, it did. The focus now shifts to how effectively the network implements its promised improvements and maintains stability in future upgrades. Before trading SUI, be sure to conduct thorough research and follow the latest market updates on Bitrue.

FAQ

What caused the Sui mainnet outage?

The outages were caused by bugs introduced in the SUI v1.72 software upgrade, specifically a gas logic bug and a randomness protocol bug.

Was the SUI network hacked?

No. The incident was not caused by a hack, exploit, or cyberattack. It was a software-related reliability issue affecting validator operations.

Did users lose funds during the outage?

No. User funds remained safe throughout the incident. No transactions were reversed, and no assets were lost.

Why did the SUI price fall during the outage?

The SUI price reaction was driven by concerns about network reliability, temporary disruption of DeFi services, exchange restrictions, and reduced investor confidence.

How can I trade SUI after the outage?

Traders should monitor network stability, validator performance, ecosystem recovery metrics, and key technical levels before making trading decisions.

Disclaimer: The views expressed belong exclusively to the author and do not reflect the views of this platform. This platform and its affiliates disclaim any responsibility for the accuracy or suitability of the information provided. It is for informational purposes only and not intended as financial or investment advice.