Sui Mainnet Recovers After 6-Hour Network Stall: No Funds at Risk

On January 14, 2026, Sui Mainnet faced a significant disruption, leaving the network stalled for roughly six hours. The incident was caused by an internal divergence in validator consensus processing, which prevented new checkpoints from being certified.

However, the safety mechanisms of the network ensured that the funds of the users remained safe. The RPC reads continued to display the last certified state, and there were no certified transactions that were reversed. 

The pause in the network was not caused by congestion or an attack on the network, and this shows that Sui is more concerned with safety than continuity.

Also Read: SUI Hits Major Milestone with 21Shares 2x Leveraged ETF Launch

Rare Sui Consensus Bug Triggers Network Divergence

The issue arose due to a rare issue in the consensus commit logic. There were some garbage collection scenarios where the optimizations caused the validators to come to different conclusions. 

This resulted in the network being unable to certify the checkpoints, as more than one-third of the stake signing different checkpoint digests.

The layered consensus, ordering, deterministic commits, quarantine, and quorum-based certification in Sui paused automatically due to the issue of inconsistent checkpoints.

Analysts familiar with how blockchains function said that this type of shutdown is disruptive, but it is a good example of how safety layers are useful. Instead of risking a broken data set, the shutdown allowed the problem to be solved.

Structured Recovery Restores Network Consensus

The recovery process occurred in a series of steps. First, the Sui team identified where the problem occurred and corrected the faulty consensus data. The validators tested the correction with a small and safe deployment, checking the production of checkpoints and the consensus logs.

After the correction was shown to be safe, the validators upgraded to the corrected software, safely replayed the consensus, and resumed signing checkpoints. The network was fully restored when enough validators reached consensus on the checkpoint digests.

Looking ahead, Sui plans to reduce the time it takes to recover from occurrences like this in the future. They will be able to identify issues sooner, work on improving their automated tools to resolve inconsistent state issues, and increase their random testing to identify consensus bugs.

Also Read: SUI Price Holds Key Support Zone as Market Awaits Next Breakout