Deep Tide TechFlow News, January 16, The Sui Foundation reports that the Sui mainnet experienced approximately 6 hours of network downtime on January 14, 2026. The cause was internal disagreement in validator consensus processing, which prevented the certification of new checkpoints. This outage was unrelated to network congestion or transaction volume, and was instead due to an edge case error in the consensus submission logic.
During the downtime, transaction submissions timed out and could not be executed, but the network security mechanisms continued to operate normally, ensuring the complete safety of user funds, with no state rollbacks or double payments. Read operations still provided the last certified state throughout the event.
Sui engineers and the validator community acted quickly, diagnosing the issue, implementing fixes, and deploying updated binary files to successfully restore the network. The team is now working on improving detection and recovery speed, developing automation tools, and strengthening testing and validation to reduce recovery times for similar incidents in the future.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Sui Release Incident Report: The mainnet experienced a 6-hour outage and has now resumed normal operation, with user funds remaining secure.
Deep Tide TechFlow News, January 16, The Sui Foundation reports that the Sui mainnet experienced approximately 6 hours of network downtime on January 14, 2026. The cause was internal disagreement in validator consensus processing, which prevented the certification of new checkpoints. This outage was unrelated to network congestion or transaction volume, and was instead due to an edge case error in the consensus submission logic.
During the downtime, transaction submissions timed out and could not be executed, but the network security mechanisms continued to operate normally, ensuring the complete safety of user funds, with no state rollbacks or double payments. Read operations still provided the last certified state throughout the event.
Sui engineers and the validator community acted quickly, diagnosing the issue, implementing fixes, and deploying updated binary files to successfully restore the network. The team is now working on improving detection and recovery speed, developing automation tools, and strengthening testing and validation to reduce recovery times for similar incidents in the future.