Sui blames consensus bug for Jan. 14 six-hour network outage

Sui has published a post-mortem explaining the six-hour network outage on Jan. 14, confirming a consensus bug halted activity but user funds were safe.

Sui has published a post-mortem detailing the cause of the network outage that disrupted mainnet activity on Jan. 14, 2026, temporarily stopping transactions and checkpoint certification across the blockchain.

In a blog post published on Jan. 16, the team said the issue was caused by a divergence in internal consensus among validators. It stressed that the interruption was not linked to heavy network usage, external attacks, or security breaches, and that user funds remained safe throughout the incident.

What went wrong

According to Sui (SUI), an edge-case bug in the way consensus commits were processed caused validators to reach different conclusions when handling certain conflicting transactions. As a result, validators began producing different checkpoint candidates, making it impossible to reach the stake-weighted agreement required to certify a new checkpoint.

When validators detected that a significant portion of the stake was signing conflicting checkpoint data, the network halted by design. This pause prevented an inconsistent state from being finalized, even though it meant block production and transaction execution stopped.

Transaction submissions timed out during the outage, but read-only queries kept serving the final certified state. 

On-chain activity was halted and an estimated $1 billion in value remained temporarily inactive during the roughly six-hour disruption. No certified transactions were reversed, nor did forks take place despite the halt.

Recovery and improvements

Recovery began once the root cause was identified. Validators removed the incorrect consensus data, applied a fix to the commit logic, and replayed the chain from the point of divergence.

After a successful canary deployment by Mysten Labs validators, the wider validator set upgraded and resumed checkpoint signing, allowing the network to return to normal operation later that day.

Sui said the incident confirmed that its safety-first design worked as intended by prioritizing consistency over uptime. At the same time, the team acknowledged the need to shorten recovery times. 

Improved automation for validator operations, increased testing to identify similar consensus edge cases before they reach the mainnet, and early detection of checkpoint inconsistencies are among the planned changes. 

Following a brief incident in late 2024, the Jan. 14 outage was the second major disruption on Sui since its launch in 2023. SUI’s price saw limited volatility, suggesting the market largely viewed the issue as operational rather than structural.