cryptotech.gg-logo cryptotech.gg-logo
  • News
  • Markets
    • Crypto Stocks
    • Price Analysis
    • Price Calculator
    • Price Prediction
  • Cryptocurrency
    • Bitcoin
      • Bitcoin Cash
      • BNB
    • Dogecoin
    • Ethereum
    • Litecoin
    • Shiba Inu Coin
    • Solana
    • TRON
    • USD Coin
  • Crypto Wallets
  • Crypto Gaming
    • GameFi
  • Reviews
  • Best Anonymous Casinos
  • Top Bitcoin Casinos
  • Top Mobile Casinos
  • Top New Casinos 2025
Reading: Sui Network Suffers Second Outage in 48 Hours: What Caused the Latest Halt?
Share
Font ResizerAa
Crypto TechCrypto Tech
  • News
  • Markets
  • Cryptocurrency
  • Crypto Wallets
  • Crypto Gaming
  • Reviews
  • Best Anonymous Casinos
  • Top Bitcoin Casinos
  • Top Mobile Casinos
  • Top New Casinos 2025
Search
  • News
  • Markets
    • Crypto Stocks
    • Price Analysis
    • Price Calculator
    • Price Prediction
  • Cryptocurrency
    • Bitcoin
    • Dogecoin
    • Ethereum
    • Litecoin
    • Shiba Inu Coin
    • Solana
    • TRON
    • USD Coin
  • Crypto Wallets
  • Crypto Gaming
    • GameFi
  • Reviews
  • Best Anonymous Casinos
  • Top Bitcoin Casinos
  • Top Mobile Casinos
  • Top New Casinos 2025
CryptoTech | All Rights Reserved.

Sui Network Suffers Second Outage in 48 Hours: What Caused the Latest Halt?

Last updated: May 30, 2026 4:57 am
Published: May 30, 2026
Share
Sui Network Suffers Second Outage in 48 Hours: What Caused the Latest Halt?
Sui Network Suffers Second Outage in 48 Hours: What Caused the Latest Halt?


Your browser does not support the video tag.

The Sui layer-1 blockchain has experienced a frustrating sense of déjà vu, suffering a second network stall on Friday just a day after a significant multi-hour outage. If you were trying to transact on the network, you likely noticed that block production temporarily halted, leaving the network paused for over three and a half hours. According to on-chain data from the Suiscan block explorer, the disruption began when the last block was produced at roughly 11:51 UTC, with normal mainnet activity finally resuming around 3:30 UTC.

Contents
  • The Root Cause Behind the Repeated Stalls
  • Contextualizing Sui’s Network Reliability in 2026

This recent downtime marks the second major network disruption for the protocol in 2026, causing understandable concern among users and developers who rely on its high-speed infrastructure. However, the Sui development team was quick to communicate and identify the culprit, tracing the issue back to a specific software update that had already caused trouble earlier in the week.

The Root Cause Behind the Repeated Stalls

Both Thursday’s nearly six-hour downtime and Friday’s sudden halt trace back to the exact same software bug introduced in the network’s 1.72 release. This specific update rolled out new logic for handling address balances and gas charging. Unfortunately, a critical crash bug buried deep within this new gas charging logic triggered Thursday’s initial collapse.

When the network went down on Thursday, validators implemented a quick interim fix designed to restore functionality as rapidly as possible. At the time, the development team noted that this temporary patch carried a relatively low probability of causing further network disruptions. Unfortunately, that unlikely scenario played out on Friday. The good news for the ecosystem is that a comprehensive, long-term software fix has now been successfully deployed and adopted by the vast majority of Sui’s mainnet validators, which should permanently prevent this specific bug from bringing the chain down again.

Contextualizing Sui’s Network Reliability in 2026

While this week’s back-to-back outages were directly related to the gas charging update, they arrive on the heels of another significant disruption earlier this year. Back in January, the Sui network went offline for over six hours due to a complex consensus bug. In that instance, validators submitted conflicting transactions to the protocol’s checkpoint system. The network’s built-in quarantine mechanisms worked exactly as designed—preventing a permanent blockchain fork—but they did so at the cost of halting all progress until consensus could be safely reached. Crucially, the team confirmed that the January incident was not caused by high traffic congestion, and user funds were never at risk.

These growing pains highlight the unique structural challenges faced by modern, high-throughput smart contract blockchains. Building infrastructure that layers data availability, transaction execution, and validator consensus introduces incredible speed, but it also creates multiple potential points of technical failure. Of course, downtime isn’t a problem exclusive to decentralized networks. Even massive centralized crypto platforms face unexpected hurdles, such as when Coinbase suffered a temporary service disruption this past May due to an Amazon Web Services (AWS) outage. As the Sui network continues to mature and patch these edge-case bugs, the successful rollout of Friday’s permanent fix marks a vital step toward long-term stability.


Your browser does not support the video tag.

TAGGED:network stallSui blockchainSui networkSui outage
Share This Article
Facebook Email Copy Link Print
Previous Article Texas Shifts $10M Bitcoin Strategy: Trading BlackRock’s ETF for Direct Crypto Custody Texas Shifts $10M Bitcoin Strategy: Trading BlackRock’s ETF for Direct Crypto Custody


Your browser does not support the video tag.

Price Chart

# Name Price Changes 24h Market CAPVolumeSupply
cryptotech.gg-logo cryptotech.gg-logo

Cryptotech.gg is the most genuine and authentic crypto website, that provides the best insights of market along with the latest news of trends.

Explore

  • Trending News
  • Top Litecoin Casinos
  • Best Ethereum Casinos
  • Top New Casinos 2025

CRYPTOTECH.GG​

  • About Us
  • Terms & Conditions
©Crypto Tech | All Rights Reserved.
  • Trending News
  • Top Litecoin Casinos
  • Best Ethereum Casinos
  • Top New Casinos 2025
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?