Sui suffered two block production outages in two days, with total downtime reaching about 9.5 hours. The latest incident began at 11:51 UTC on Friday, when new blocks stopped being added, and normal operation was restored only after 3:30 UTC.
In a network statement, Sui said it first implemented a temporary fix and described the chance of additional issues as low. It also said that most validators have now rolled out a permanent software correction. The previous disruption had taken place on Thursday and lasted nearly six hours, traced to a critical bug in gas fee calculation software.
Two straight days of block production problems
The back-to-back outages put fresh attention on the network’s technical stability. Before the latest stoppage, the report said Sui had already gone through its second major outage of 2026, adding to concerns around reliability.
Based on the timeline in the report, Thursday’s interruption lasted close to six hours, while Friday’s halt ran for roughly 3.5 hours. The accompanying table listed the cause of the Friday event as a validator error. In practical terms, Sui lost block production capability twice in a very short span.
January outage was tied to a consensus failure
Earlier in 2026, Sui also experienced a major disruption that halted block production for more than six hours. That episode was linked to a serious consensus failure. Validators submitted conflicting transactions for approval at the same time, and the network could not reach agreement on how to process them.
A later analysis said the system’s control and quarantine mechanisms were triggered during that event. According to the Sui team, user funds were not at risk and no completed transactions were reversed. The team also said the January outage was not caused by congestion. Even though the chain stopped completely for several hours, the handling prevented any visible chain split.
Outages keep exposing infrastructure pressure points
The incidents highlight the operational risks that can surface in both decentralized blockchains and centralized crypto platforms. On scalable blockchain networks, failures can emerge in validator data sharing, transaction execution, or collective decision-making. Those issues do not need heavy traffic to become disruptive.
The report also pointed to a centralized example. In May, Coinbase was forced into “auction” mode and temporarily suspended user transactions because of an Amazon Web Services infrastructure outage. The architecture is different, but service interruptions can still happen when critical underlying components fail.