Chronology of the Sui Network Disruptions
According to the Suiscan block explorer, the last block before Friday’s disruption was produced at approximately 11:51 UTC. Mainnet activity resumed around 15:30 UTC. The Sui team confirmed that the incident was directly tied to the software update deployed to address Thursday’s critical bug.
- Thursday Outage: ~6 hours (Gas charging logic bug)
- Friday Outage: ~3.5 hours (Interim software fix issue)
- January Outage: ~6 hours (Consensus bug)
The project’s developers explained that the interim patch had a “low probability” of causing a network disruption. However, the unexpected code behavior still triggered a halt in block production. Currently, a permanent software fix has been successfully implemented by a majority of Sui validators, restoring normal operations.
“High-throughput Layer-1 networks push the limits of execution speed, but this architectural complexity introduces multiple points of failure. When validators struggle to reach consensus due to minor software updates, it highlights the delicate balance between scalability and stability.”
Systemic Challenges for Modern Blockchains
This incident marks the second major technical crisis for SUI in 2026. Earlier in January, the network went offline for over six hours due to a consensus bug where validators submitted conflicting transactions to the protocol’s checkpoint mechanism.
The developers emphasized that user funds were never at risk during these incidents, and no certified transactions were rolled back. Nonetheless, frequent blockchain halts raise questions among institutional investors regarding the reliability of the underlying infrastructure.
Frequently Asked Questions (FAQ)
What caused the Sui network outage on Friday?
The outage was caused by an unexpected issue with the interim software fix deployed to resolve Thursday’s gas charging logic bug.
Were user funds at risk during the Sui downtime?
No, the Sui team confirmed that user funds remained completely secure, and the network’s quarantine mechanisms prevented any user-visible forks.
How did validators resolve the issue?
The majority of validators quickly deployed a long-term software patch, which successfully restored consensus and block production.
