Sui Network Encounters Second Outage After Thursday Downtime

The Sui layer-1 blockchain faced another disruption this week, triggering a network stall that halted block production for more than three and a half hours before activity resumed. The incident, detailed by the Sui team and reflected in the network’s status dashboards, marks the second consecutive day of instability for the chain’s mainnet validators.

According to Sui status updates and the Suiscan block explorer, the last block prior to the disruption was produced at roughly 11:51 UTC on Friday, with network activity picking up again around 03:30 UTC. The team attributed the stall to the interaction between the recently released v1.72 software and the network’s address balances and gas charging logic. An interim fix had been deployed to restore functionality ahead of a more durable solution adopted by a majority of validators.

“Both today’s and yesterday’s halts are due to the interaction of the 1.72 release, which introduced address balances and gas charging logic. Yesterday’s implemented fix was an interim measure designed to restore functionality to the network.”

The interim patch was described as having a low probability of causing further disruption, with the long-term software fix now implemented by most validators. The incident follows a sequence of disruptions that began with Thursday’s outage, which was caused by a crash bug in the gas charging logic and led to a nearly six-hour downtime, according to the Sui team.

Beyond these events, Sui’s broader 2026 disruption history includes a high-profile outage in January 2026. The network went offline for more than six hours due to a consensus bug—validators submitted conflicting transactions to the protocol’s checkpoint mechanism, preventing the network from reaching the required consensus threshold. The post-mortem on that incident emphasized that the issue was contained by Sui’s checkpoint certification and quarantine mechanisms, which prevented a user-visible fork but halted progress in the process. The team stressed that user funds were never at risk and that no certified transactions were rolled back.

These recent incidents highlight the inherent fragility that can accompany high-throughput blockchain systems, where data availability, execution, and validator consensus layers intersect. The Sui team’s emphasis on checkpoint certification and quarantine underscores the defensive design choices intended to minimize user impact even when the network halts. Still, outages on a public network ripple outward, affecting centralized services that depend on live blockchain data and uptime. The episode also calls attention to the broader ecosystem, where outages at major service providers—such as cloud platforms—can compound the disruption for users and exchanges alike. For example, Coinbase faced a temporary service disruption in May due to an AWS outage, illustrating how a single failure point in the infrastructure stack can affect trading and liquidity even when the underlying blockchain remains theoretically resilient.

Key takeaways

• The latest Sui mainnet stall lasted over three and a half hours, with block production halted and later resumed after an interim patch and a longer-term fix.
• The disruption is attributed to the interaction between the 1.72 release—specifically address balances and gas charging logic—and the network’s existing execution and consensus flow.
• A durable software fix has been adopted by a majority of validators, following an interim repair rated as having a low likelihood of introducing new disruptions.
• The Friday incident follows Thursday’s six-hour outage caused by a crash bug in gas charging logic, and January’s six-plus hour stall caused by a consensus bug in the checkpoint mechanism.
• Analysts and developers note that outages on public blockchains can ripple into centralized services, highlighting the importance of robust recovery mechanisms and cross-layer resilience.

Context and implications for validators and users

From a technical perspective, Sui’s recurrent outages appear tied to how new software revisions interact with core network logic—specifically around how balances are tracked and how gas is charged. The 1.72 release introduced new balance-tracking and gas-charging semantics, and the subsequent halts suggest that the edge cases in those changes require careful handling to avoid cascading pauses in block production. The Sui team’s post-mortem emphasizes that the interim fix was designed to restore functionality quickly, while the long-term patch has now been broadly deployed to reduce the chance of another disruption.

For developers and validators, these events underscore the importance of rigorous rollout processes for critical protocol changes, especially on networks that aim for high throughput and low-latency finality. They also highlight the value of quarantine and checkpoint mechanisms as safeguards that can prevent user-visible forks even if network progress stalls. Investors and users should watch how quickly the ecosystem stabilizes after major releases and whether any secondary issues emerge as the new code paths become fully saturated in production workloads.

Looking ahead, the Sui network’s roadmap will likely focus on hardening the 1.72-induced changes, validating their behavior across a range of transaction loads, and ensuring that governance and operator tooling align to minimize operator risk during upgrades. Observers will also be watching to see whether further incidents emerge as validators complete the switch to the long-term fix and begin stress-testing the network under real-world conditions.

In the meantime, the episodes serve as a reminder of the delicate balance in building scalable, developer-friendly blockchains: the pursuit of higher throughput must be matched by robust validation, fault tolerance, and rapid, transparent post-mortems that translate into stronger resilience over time.

Readers should keep an eye on Sui’s official status updates and validator communications as the ecosystem digests the full implications of the latest patching cycle and gauges the network’s readiness to sustain higher loads without recurring interruptions.